python / python/mypy

Meta issue tracker, pt 2

Open
#16,472 1 comment 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

meta
Dominant language
Python
Stars
20.6k
Forks
3.3k
PR merge metrics
PR metrics pending

Description

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)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the still-open linked issues under Type System Features, Behaviour changes, UI, Gradual typing, and Misc, along with their referenced discussions. This tracker names no files or tests; completion requires resolving the selected outstanding items or moving them into separately scoped work.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.