Running mypy on code that uses the latest version of click-didyoumean fails with the error message "module is installed, but missing library stubs or py.typed marker". It seems that this package gained type annotations in v0.2.0 (ref: #6), but because there is no py.typed file, mypy will not use the annotations when type-checking code that uses it.
To resolve this, please do the following:
[ ] Add an empty file named py.typed inside the click_didyoumean package.
[ ] Ensure that the src/click_didyoumean/py.typed file is included in sdists & wheels built from the project. This may involve configuration specific to your build backend (poetry) that is beyond the scope of this comment.
You can list the contents of an sdist (the dist/click_didyoumean-{version}.tar.gz file created when building the project) by running tar ztf dist/click_didyoumean-{version}.tar.gz on it.
You can list the contents of a wheel (a dist/click_didyoumean-{version}-*-*-*.whl file created when building the project) by running zipinfo -1 dist/click_didyoumean-{version}-*-*-*.whl on it.
Running mypy on code that uses the latest version of
click-didyoumeanfails with the error message "module is installed, but missing library stubs or py.typed marker". It seems that this package gained type annotations in v0.2.0 (ref: #6), but because there is nopy.typedfile, mypy will not use the annotations when type-checking code that uses it.To resolve this, please do the following:
py.typedinside theclick_didyoumeanpackage.src/click_didyoumean/py.typedfile is included in sdists & wheels built from the project. This may involve configuration specific to your build backend (poetry) that is beyond the scope of this comment.dist/click_didyoumean-{version}.tar.gzfile created when building the project) by runningtar ztf dist/click_didyoumean-{version}.tar.gzon it.dist/click_didyoumean-{version}-*-*-*.whlfile created when building the project) by runningzipinfo -1 dist/click_didyoumean-{version}-*-*-*.whlon it.Further references: