Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`py.typed` not getting distributed
See original GitHub issueIt seems that the py.typed file is not getting distributed, so mypy is not recognizing installed rich-click as being typed. I think you need to explicitly add it to package_data (options.package_data in setup.cfg).
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:11 (11 by maintainers)
Top Results From Across the Web
My Python multi-module package won't distribute with a py ...
However when I distribute the package, it doesn't include any of the py.typed files. I have no idea why this is, and it's...
Read more >PEP 561 – Distributing and Packaging Type Information
However, there is no standard method to distribute packages with type information. Also, if one wished to ship stub files privately the only ......
Read more >Missing py.typed declaration? #193 - encode/httpx - GitHub
mypy is complaining about not being able to find type annotations for httpx : error: Cannot find module named 'httpx'.
Read more >Don't forget `py.typed` for your typed Python package
It's faily simple to include this file: just touch a py.typed file in your package directory and include it in your distribution.
Read more >packaging python typed code (intermediate) anthony explains ...
today I talk about how to package up typed code -- either inline types or typing stubs and distribute it via pypi!
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
For posterity, I was eventually able to reproduce locally #75 being the solution. Interestingly,
package_data={"rich-click": ["py.typed"]}insetup.pysilently fails to addpy.typed, whilerich-click = py.typedinsetup.cfg’s[options.package_data]automatically does the conversion torich_click(though giving a warning) and does add thepy.typed.(type checking? ok, it was tenuous…)