json.dump() ignores its 'default' option when serializing dictionary keys

Abierto
#63,020 11 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
backend

Línea de trabajo

Start with the json.dump() and encoder implementation, then review the linked PR gh-119984 and the proposed json-default-dict-keys.diff and json-default-tests.diff files. Check how dictionary keys are serialized in both the default and C implementations. Done means the default option is honored for dictionary keys and regression coverage passes for both paths.

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

Descripción

3.10 3.11 3.9 (EOL) stdlib type-bug
BPO 18820
Nosy @rhettinger, @etrepum, @pitrou, @ezio-melotti, @tifv, @berkerpeksag, @serhiy-storchaka, @iritkatriel
Files
  • json-default-dict-keys.diff: applies to default, does not fix C implementation
  • json-default-tests.diff: proposed tests (for default)
  • 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-08-23.10:30:29.980>
    labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
    title = "json.dump() ignores its 'default' option when serializing dictionary keys"
    updated_at = <Date 2022-03-13.20:16:36.622>
    user = 'https://github.com/tifv'
    

    bugs.python.org fields:

    activity = <Date 2022-03-13.20:16:36.622>
    actor = 'iritkatriel'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2013-08-23.10:30:29.980>
    creator = 'july'
    dependencies = []
    files = ['31437', '31450']
    hgrepos = []
    issue_num = 18820
    keywords = ['patch']
    message_count = 8.0
    messages = ['195957', '195958', '196022', '196036', '263013', '263019', '263025', '415093']
    nosy_count = 11.0
    nosy_names = ['rhettinger', 'bob.ippolito', 'pitrou', 'ezio.melotti', 'cvrebert', 'july', 'docs@python', 'berker.peksag', 'serhiy.storchaka', 'Erwin Mayer', 'iritkatriel']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue18820'
    versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
    

    Linked PRs
    • gh-119984
    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.