Closed EternityForest closed 3 months ago
Typeguard's own test suite would fail on Python 3.10 if this was the case. How did you install it?
That is rather odd and a very good point! I'm not sure why it's so random.
I installed via Poetry, in a project with about 100 other dependencies, but I could do some more digging and try to build a minimal reproduction if needed.
It seems to also occur outside of the virtualenv too, so I would imagine it could be some distro specific nonsense or some other package that breaks stuff if it's present, since the behavior wasn't always there.
For now I'm monkeypatching version() to raise an error if it would normally return None, and everything works fine.
I haven't searched all the different discussions threads but it seems like they are/were talking about making returning None a normal behavior though?
If the package was installed properly, the version("typeguard")
should return the version properly. If this is not happening, then you need to figure out why (or provide a MWE).
Closing as stale.
Things to check first
[X] I have searched the existing issues and didn't find my bug already reported there
[X] I have checked that my bug is still present in the latest release
Typeguard version
4.2.0, 4.2.1
Python version
3.10.12
What happened?
I believe this is Python 3.10 specific due to: https://github.com/python/typeshed/issues/7513
How can we reproduce the bug?