-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
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
mypy says "no type hints or library stubs" although it parses package's .pyi #2194
Comments
Did you include a |
@yanoom was this ever resolved? |
I am facing the same issue with the |
@sobolevn can you provide a bit more context please? @yanoom I believe this was resolved in #2000 for If you are building the wheen under PEP 517, you should update your [build-system]
requires = ["poetry-core>=1.0.0"]
build-backend = "poetry.core.masonry.api" |
@abn here's the full reproduction: dry-python/returns#659 Update: solved, by typeddjango/pytest-mypy-plugins#40 |
@sobolevn am I correct in understanding that this was a plugin issue caused due to poetry's editable installs using dist-info insted of setuptool's |
Yes, exactly. We needed to add a hack around |
@sobolevn so I can close this issue then? Assuming there is nothing to be done on the poetry side since we are following standard mechanisms to load path into python site. |
Yeap, this can be closed. Solution: use |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
-vvv
option).Issue
We are in the process of releasing our library, called "Pyctuator".
I successfully created stubs for the package using stubgen.
I added the
MYPYPATH
environment variable with the location of the previously created "stub output folder" for mypy to find the stubs.I use
poetry run mypy
on an example application that uses our new package:I see that mypy is parsing the desired
pyctuator.pyi
But still fails in the end stating that no type hints or library stubs have been found:
Your assistance is highly appreciated- thanks!
:)
The text was updated successfully, but these errors were encountered: