zipfile.write, arcname should be allowed to be a byte string

Open
#54,966 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend

Research direction

Start at the zipfile.write entry point and review the surrounding standard-library behavior for arcname types. Done means byte-string arcnames are accepted as requested and regression coverage demonstrates the behavior; the issue is marked “test needed.”

Written by the indexing model from the issue text.

Description

pending stdlib type-feature
BPO 10757
Nosy @loewis, @bitdancer

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2010-12-22.12:44:03.540>
labels = ['type-bug', 'library']
title = 'zipfile.write, arcname should be allowed to be a byte string'
updated_at = <Date 2016-01-02.23:23:30.550>
user = 'https://bugs.python.org/connexion2000'

bugs.python.org fields:

activity = <Date 2016-01-02.23:23:30.550>
actor = 'Patrik Dufresne'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2010-12-22.12:44:03.540>
creator = 'connexion2000'
dependencies = []
files = []
hgrepos = []
issue_num = 10757
keywords = []
message_count = 7.0
messages = ['124499', '124518', '124519', '124641', '124686', '124690', '257385']
nosy_count = 6.0
nosy_names = ['loewis', 'aimacintyre', 'r.david.murray', 'connexion2000', 'ozialien', 'Patrik Dufresne']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue10757'
versions = ['Python 3.1', 'Python 3.2']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.