We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
According to PEP 561 stub-only package:
The name of the stub package MUST follow the scheme foopkg-stubs for type stubs for the package named foopkg.
However if we invoke mypy on such package providing only path it fails with
*-stubs is not a valid Python package name
This can be reproduced on the example package:
git clone https://github.com/ethanhs/stub-package cd stub-package mypy ./typedpkg-stubs typedpkg-stubs is not a valid Python package name
Invoking mypy with -p option works
mypy
-p
mypy -p typedpkg-stubs Success: no issues found in 2 source files
but the former behavior is rather confusing.
Expected behavior:
*-stubs
Tested with:
The text was updated successfully, but these errors were encountered:
Recognize -stubs directories as valid package directories (#9445)
b707d29
Fixes #8229
Successfully merging a pull request may close this issue.
According to PEP 561 stub-only package:
However if we invoke mypy on such package providing only path it fails with
This can be reproduced on the example package:
Invoking
mypy
with-p
option worksbut the former behavior is rather confusing.
Expected behavior:
*-stubs
paths as roots of stub-only packages.Tested with:
The text was updated successfully, but these errors were encountered: