warnings should provide a public API for accessing its option parsing code

Abierto
#52,224 19 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
api

Línea de trabajo

Read the warnings module's option-parsing implementation and the linked warnings_opt_parse_API patches first, since the issue does not name a current source file or test. Done requires an agreed public API for this parsing behavior, documented semantics, and coverage for the exposed interface.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

stdlib type-feature
BPO 7976
Nosy @brettcannon, @ncoghlan, @vstinner, @ericvsmith, @merwok, @bitdancer, @masklinn, @berkerpeksag
Files
  • warnings-option.diff: Addition of an Option instance to warnings for python 2's trunk.
  • warnings_opt_parse_API.patch: Expose command line parsing facilities
  • warnings_opt_parse_API-2.patch: Added doc.
  • warnings_opt_parse_API-3.patch
  • warnings_opt_parse_API-4.patch: Removed old private exception and function. Typo in the doc
  • warnings_opt_parse_API-5.patch: WarningsOptParsingError -> WarningsOptionParsingError + cosmetics
  • warnings_opt_parse_API-6.patch: renamed the function to parse_option
  • warnings_opt_parse_API-7.patch
    		•

    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-02-21.16:55:32.650>
labels = ['type-feature', 'library']
title = 'warnings should provide a public API for accessing its option parsing code'
updated_at = <Date 2019-07-29.11:30:38.903>
user = 'https://github.com/masklinn'

    bugs.python.org fields:

    activity = <Date 2019-07-29.11:30:38.903>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2010-02-21.16:55:32.650>
creator = 'xmorel'
dependencies = []
files = ['16279', '28153', '28154', '28158', '28160', '28173', '28174', '28175']
hgrepos = ['161']
issue_num = 7976
keywords = ['patch']
message_count = 19.0
messages = ['99670', '99893', '99896', '99897', '99921', '99930', '176607', '176608', '176610', '176615', '176624', '176628', '176630', '176639', '176723', '176730', '176731', '176735', '348615']
nosy_count = 9.0
nosy_names = ['brett.cannon', 'ncoghlan', 'vstinner', 'eric.smith', 'eric.araujo', 'r.david.murray', 'xmorel', 'berker.peksag', 'bruno.dupuis']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue7976'
versions = ['Python 3.5']

    Lenguaje dominante
    Python
    Estrellas
    77.2k
    Forks
    36k
    Merge medio
    1 d 9 h
    PR fusionados (30 d)
    558

    Guía de contribución

    Abrir la guía de contribución

    Primeros pasos

    1. Lee el issue completo y luego la guía de contribución del proyecto.
    2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
    3. Haz un fork del repositorio y trabaja en una rama.
    4. Abre un pull request que haga referencia al número del issue.

    Más de python/cpython

    Todos los issues de python/cpython

    Issues similares

    Más issues de Python

    Recibe los nuevos issues en tu correo

    Un resumen breve de issues de GitHub para principiantes.