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.
Package is not PEP 561 compliant
See original GitHub issueHi, I notice that this package isn’t PEP 561 compliant, making mypy (v0.782, Python 3.7) unable to detect type annotations even though they exist in the code. A remedy is to put a py.typed file in the package directory, as explained in https://mypy.readthedocs.io/en/stable/installed_packages.html#making-pep-561-compatible-packages. I may be able to make a PR for this, so let me know if you’re OK with it.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Is there a best practice to make a package PEP-561 compliant?
Is there a best practice to make a package PEP-561 compliant? · Run stubgen to create stub files. · Create py.typed files in...
Read more >PEP 561 – Distributing and Packaging Type Information
The proposed scheme of indicating support for typing is completely backwards compatible, and requires no modification to package tooling. A ...
Read more >Package is not PEP 561 compliant · Issue #72 · rspeer/ordered-set ...
Hi, I notice that this package isn't PEP 561 compliant, making mypy (v0.782, Python 3.7) unable to detect type annotations even though they...
Read more >Using installed packages - mypy 0.991 documentation
PEP 561 specifies how a package can declare that it supports type checking. New versions of stub packages often use type system features...
Read more >Is there a best practice to make a package PEP-561 compliant?
Is there a best practice to make a package PEP-561 compliant? Answer a question I'm writing a Python project which is published as...
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
Fixed in 4.1. I had a more compelling reason to repackage ordered-set (using flit instead of setuptools), and now the package has a PEP561 compatible structure.
I said more about this on the PR, but this is something I’d rather revisit if there’s a more compelling reason to repackage ordered-set. I’m too disappointed by the state of packaging of types to want to change the shape of this package for that alone.