Yak

@barbeau Outside of updating the ID mapping, should the missing types be added with the corresponding flags, strings and entry in the FAQ? Are missing today types for: - ASECNA...

This can be closed imo, mypy is now properly working with `__pypackages__`

This would be great, and I'm interested for a workaround for `*type[Ts]` if any.

Yes, I asked because it is already a special case, otherwise the argument of genericity would prevail

> Implement a CLI command for listing all implicitely disabled rules (or collections, if all rules in a collection are disabled). I like this idea, it can be useful outside...

Isort uses a list of known stdlib modules for each python version: https://github.com/PyCQA/isort/tree/main/isort/stdlibs While ruff seems to use a static list for every python version: https://github.com/charliermarsh/ruff/blob/main/src/python/sys.rs Is it worth doing...

Should another issue be opened to respect the `target-version` for the imports or is supporting the latest stdlib enough?

I fully agree with the intent `2.`, no doubt about it. I'm mixed about `1.` It is easily fixed if you run the formatter before the linter, thing that was...

If we imagine a world in which `format` and `check` are combined, I believe we can expect `format + fix` according to the rules, and the the remaining violations are...

Anyways, thank you very much for the openness and allowing discussions about all this, as well as the quick iterative fixes