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
I'm interested in using cloudpathlib in my project, but I'm currently not able to because of the following error:
[file in my project]:8:1: error: Skipping analyzing "cloudpathlib": module is installed, but missing library stubs or py.typed marker [import]
According to the mypy documentation, this is because cloudpathlib doesn't include type hints or declare itself as a PEP 561 compliant stub package.
Is cloudpathlib supposed to work with type checkers? I see that the code has type hints, so I'm surprised that it doesn't work for me out of the box.
The text was updated successfully, but these errors were encountered:
It looks like it's as easy as adding an empty file called py.typed in the cloudpathlib directory, and adding package_data={"cloudpathlib": ["py.typed"]}) to setup.py. (See https://blog.whtsky.me/tech/2021/dont-forget-py.typed-for-your-typed-python-package/.)
py.typed
cloudpathlib
package_data={"cloudpathlib": ["py.typed"]})
setup.py
Would you accept a PR that adds this?
Sorry, something went wrong.
Thanks for reporting! A PR is welcome.
@sid-kap This is released now in version 0.10.0 on PyPI
Awesome, thanks!!
Successfully merging a pull request may close this issue.
I'm interested in using cloudpathlib in my project, but I'm currently not able to because of the following error:
According to the mypy documentation, this is because cloudpathlib doesn't include type hints or declare itself as a PEP 561 compliant stub package.
Is cloudpathlib supposed to work with type checkers? I see that the code has type hints, so I'm surprised that it doesn't work for me out of the box.
The text was updated successfully, but these errors were encountered: