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
The Python "cryptography" package discovered new dependencies
on the Rust programming, and as a consequence several of their
previously supported architectures were degraded to Tier 3 support
or made completely unsupportable.
The text was updated successfully, but these errors were encountered:
vielmetti
changed the title
Rust in general, and
Rust in general, and pyca/cryptography dependency
Oct 18, 2021
This is an odd one; from the thread, it seems like folks were blindsided by an update to cryptography which broke their build systems, and this could indicate an availability issue because the new dependencies were missing. But I think it's more of a problem with versioning? I wonder if users either didn't pin to a particular version of cryptography, or used a rule that allowed the newer version to be used. Significantly, cryptography doesn't use semver. On a side note, they also somewhat recently changed their version scheme, causing them to go from 3.4.8 to 35.0.0(!!!).
The Python "cryptography" package discovered new dependencies
on the Rust programming, and as a consequence several of their
previously supported architectures were degraded to Tier 3 support
or made completely unsupportable.
The text was updated successfully, but these errors were encountered: