You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: