Skip to content

How should I declare versioning dependency of cryptography? #5532

@rayluo

Description

@rayluo

I'm a maintainer of some other libraries, which would take a dependency on cryptography. What versioning scheme does cryptography use? Seems not Semantic Versioning, because I see many "backward incompatible" changes without major version bump. Then, how should I declare (the upper bound) of versioning dependency of cryptography in my downstream library?

cryptography>=0.6,<???

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions