An in-place version of many bytearray methods is needed
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
Línea de trabajo
Start by reviewing the attached issue17301.diff and issue17301-2.diff, then compare their proposed bytearray methods with the current implementation and tests. Done means agreeing on the required in-place methods, implementing the complete feature, and adding or updating coverage for their behavior.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
| BPO | 17301 |
|---|---|
| Nosy | @terryjreedy, @gpshead, @vstinner, @tiran, @ezio-melotti, @methane, @vadmium, @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-02-26.20:28:43.036>
labels = ['easy', 'type-feature', 'library']
title = 'An in-place version of many bytearray methods is needed'
updated_at = <Date 2019-08-09.02:38:57.653>
user = 'https://github.com/gpshead'
bugs.python.org fields:
activity = <Date 2019-08-09.02:38:57.653>
actor = 'Philip Dye'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-02-26.20:28:43.036>
creator = 'gregory.p.smith'
dependencies = []
files = ['29825', '46137']
hgrepos = []
issue_num = 17301
keywords = ['patch', 'easy']
message_count = 13.0
messages = ['183082', '183292', '183302', '183478', '183502', '183530', '183531', '183534', '186833', '284618', '284625', '284626', '284634']
nosy_count = 11.0
nosy_names = ['terry.reedy', 'gregory.p.smith', 'vstinner', 'christian.heimes', 'ezio.melotti', 'methane', 'THRlWiTi', 'martin.panter', 'serhiy.storchaka', 'n', 'Philip Dye']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17301'
versions = ['Python 3.4']
- 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