IPv6 support for logging.handlers
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 uploaded mywork.patch and mywork2.patch alongside the logging.handlers implementation; the issue identifies IPv6 support as the goal. Check linked PR gh-154496 and the existing discussion before deciding what remains, then verify that the relevant handlers support IPv6 without regressing existing behavior.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
| BPO | 14855 |
|---|---|
| Nosy | @loewis, @gpshead, @vsajip, @pitrou |
| 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 2012-05-19.09:49:33.079>
labels = ['type-feature', 'library']
title = 'IPv6 support for logging.handlers'
updated_at = <Date 2015-02-26.16:51:07.647>
user = 'https://bugs.python.org/cblp'
bugs.python.org fields:
activity = <Date 2015-02-26.16:51:07.647>
actor = 'Thomas Bartelmess'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2012-05-19.09:49:33.079>
creator = 'cblp'
dependencies = []
files = ['25635', '25680']
hgrepos = []
issue_num = 14855
keywords = ['patch']
message_count = 13.0
messages = ['161101', '161102', '161103', '161104', '161106', '161127', '161128', '161132', '161136', '161408', '161410', '161492', '236687']
nosy_count = 6.0
nosy_names = ['loewis', 'gregory.p.smith', 'vinay.sajip', 'pitrou', 'cblp', 'Thomas Bartelmess']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue14855'
versions = ['Python 3.3']
Linked PRs
- gh-154496
- 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 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
OpenHands/extensions#626 · 1 comentario ·
-
Change observation tooltip text Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
CSCfi/sd-search-api#39 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
-
please add to porn list Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
StevenBlack/hosts#3255 ·