-
-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Un-pin typeguard
#421
Comments
This is intentional. You'll notice jaxtyping is also pinned to the same version. See threads like patrick-kidger/jaxtyping#124 (comment) and agronholm/typeguard#353. The quick summary is that later versions of typeguard seem to do things that are incompatible with jaxtyping etc. FWIW typeguard v2.13.3 seems to have worked robustly in all use-cases I've had for it. |
Thanks for the explanation! And the references ❤️ Hopefully the issue can eventually be resolved upstream... |
A solution is possible: #579 |
diffrax/pyproject.toml
Line 26 in 80d1f34
Why is
typeguard
pinned to an exact version, especially one that is so old?It's generally considered very bad packaging practice to pin to exact versions as it's ~never required and prevents getting even security patches without publishing a new release.
Also, it's ancient and won't be getting any updates - current HEAD is 4.2.1:
Originally posted by @dhirschfeld in #364 (comment)
The text was updated successfully, but these errors were encountered: