permissions too restrictive in zipfile.writestr
Offen
Dieses Issue hat noch niemand übernommen.
3.11
stdlib
type-feature
- Vorherrschende Sprache
- Python
- Sterne
- 77.2k
- Forks
- 36k
- Ø Merge
- 1 T. 9 Std.
- Gemergte PRs (30 T.)
- 558
Beschreibung
| BPO | 38886 |
|---|---|
| Nosy | @raphaeldussin, @iritkatriel |
| PRs |
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 2019-11-21.20:01:41.811>
labels = ['type-feature', 'library', '3.11']
title = 'permissions too restrictive in zipfile.writestr'
updated_at = <Date 2022-01-24.23:10:17.506>
user = 'https://github.com/raphaeldussin'
bugs.python.org fields:
activity = <Date 2022-01-24.23:10:17.506>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-11-21.20:01:41.811>
creator = 'rdussin'
dependencies = []
files = []
hgrepos = []
issue_num = 38886
keywords = ['patch']
message_count = 2.0
messages = ['357210', '411527']
nosy_count = 2.0
nosy_names = ['rdussin', 'iritkatriel']
pr_nums = ['17327']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue38886'
versions = ['Python 3.11']
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Start at the zipfile.writestr entry point and determine which permissions are currently produced and what less-restrictive behavior the issue requires. The payload names no files or tests and gives no acceptance criteria, so completion cannot be verified from the issue alone; also review the historical PR 17327 before starting.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- python
- Bereich
- backend
- Issue-Typ
- Feature
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100