Work with an extra field of gzip and zip files
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start by reviewing gzip_extra.diff and zipfile_extra.diff, then inspect README.dz and README.zip to determine the intended behavior for the gzip and zip changes. Done means the requested extra-field support is clearly agreed, implemented in the relevant standard-library modules, and validated; the payload names no tests or entry points.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
| BPO | 17681 |
|---|---|
| Nosy | @bsergean, @serhiy-storchaka |
| Files |
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 2013-04-09.15:03:01.346>
labels = ['3.8', 'type-feature', 'library']
title = 'Work with an extra field of gzip and zip files'
updated_at = <Date 2021-05-06.07:45:21.873>
user = 'https://github.com/serhiy-storchaka'
bugs.python.org fields:
activity = <Date 2021-05-06.07:45:21.873>
actor = 'nikratio'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-04-09.15:03:01.346>
creator = 'serhiy.storchaka'
dependencies = []
files = ['32653', '32654', '32655', '32656']
hgrepos = []
issue_num = 17681
keywords = ['patch']
message_count = 8.0
messages = ['186423', '190295', '190301', '203077', '365626', '391612', '393052', '393053']
nosy_count = 5.0
nosy_names = ['Benjamin.Sergeant', 'serhiy.storchaka', 'dmi.baranov', 'Jason Williams', 'amijalis']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17681'
versions = ['Python 3.8']
- Lenguaje dominante
- Python
- Estrellas
- 77.2k
- Forks
- 36k
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 558
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de python/cpython
-
docs pending
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
stdlib type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
stdlib type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
build type-bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
stdlib topic-email type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Todos los issues de python/cpython
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
PolicyEngine/policyengine-us#9559 ·
-
priority: p3
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
googleapis/librarian#7636 ·
-
from:qa priority:P2 reliability tech-debt
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
spec-kitty/spec-kitty#4874 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100