Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rust in general, and pyca/cryptography dependency #2

Open
vielmetti opened this issue Oct 18, 2021 · 2 comments
Open

Rust in general, and pyca/cryptography dependency #2

vielmetti opened this issue Oct 18, 2021 · 2 comments

Comments

@vielmetti
Copy link

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.

@vielmetti vielmetti changed the title Rust in general, and Rust in general, and pyca/cryptography dependency Oct 18, 2021
@kpcyrd
Copy link

kpcyrd commented Oct 18, 2021

I'm not sure this is an availability issue instead of "new release has additional build/runtime dependencies".

@adityasaky
Copy link
Owner

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(!!!).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants