Skip to content

Can error reporting on a package that can't be opened be improved? #16634

@gmc444-b

Description

@gmc444-b

Feature

When mypy is run against a package that's installed but isn't PEP-561 compliant, it will report that it can't find the package.

It would be better to state that the package is there, but it's not PEP-561 compliant.

Pitch

The "package not found" message is extremely confusing the first (and even the fifth) time it's encountered. Developers can waste a lot of time trying to figure out why mypy can't find the package because "it's right there! I just installed it! I can import it!"

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions