python / python/mypy

Meta issue tracker, pt 2

Abierto
#16,472 1 comentario 7 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

meta
Lenguaje dominante
Python
Estrellas
20.6k
Forks
3.3k
Métricas de merge de PR
Métricas de PR pendientes

Descripción

This is the sequel to https://github.com/python/mypy/issues/11201. It's awesome to see most of the things in that issue fixed.

Type System Features
Behaviour changes
UI
  • Per module strict=true https://github.com/python/mypy/issues/11401

    There's maybe some other UI stuff we can think about for groups of flags and error codes, as discussed in meetup. I also don't like the new --extra-checks since flag name doesn't mean anything and can't be decomposed.

  • Ability to override PEP 561 https://github.com/python/mypy/issues/8545

    It would be nice to be able to opt-in to treating packages missing py.typed as having py.typed. mypy can still provide a lot of value just based on function shape.

    Update: this is now --follow-untyped-imports (can be set per-module)

  • Exclude should imply per-module follow_import=skip https://github.com/python/mypy/issues/10377

    Currently --exclude only affects file discovery on command line, not import following. This is a source of frustration for users because the relevant modules can still end up being type checked.

  • Provide flag to generate stubs requirements https://github.com/python/mypy/issues/10600#issuecomment-950170169

    --install-types is slow, results in unstable type checking, doesn't let users manage their own envs, can fail unclearly if cache isn't written

  • Rethink stub suggestion logic https://github.com/python/mypy/issues/10619

    Our current behaviour was needed to help the migration to modular typeshed, but is not behaviour we'd have designed from scratch.

Gradual typing
Performance
Misc

See also a similar issue for mypyc here: https://github.com/mypyc/mypyc/issues/785

(other maintainers, feel free to edit)

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.

Línea de trabajo

Comienza revisando las issues vinculadas que siguen abiertas en Type System Features, Behaviour changes, UI, Gradual typing y Misc, junto con las discusiones a las que hacen referencia. Este tracker no especifica archivos ni tests; para completarlo es necesario resolver los elementos pendientes seleccionados o trasladarlos a un trabajo con un alcance separado.

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

Evaluación

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

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.