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.
[BUG] `beartype.cave` does not explicitly reexport anything *le sigh*
See original GitHub issueWe run mypy with --no-implicit-reexport to discover accidental imports from modules where a name is not publicly exposed. Beartype fails this from beartype.roar import BeartypeException, seemingly because its defined in beartype.roar._roarexc and isn’t in contained in beartype.roar.__all__.
Is there a good reason that the exceptions are defined in an other module than what’s exposed? If so, would you consider adding an __all__ to make them explicitly reexported?
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for fixing this! 🙏
Resolved by 7cd3333… yet again.
beartype.cavenow explicitly reexports its public API. In theory, this means the entire @beartype API is now explicitly reexported and should passmypy --no-implicit-reexportwithout complaint or shocking scandal.In practice, you’re our last line of defence. In @antonagestam we trust. 🗽