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

Ensure that versions are PEP 440 compliant #42

Open
vyasr opened this issue Mar 21, 2023 · 0 comments
Open

Ensure that versions are PEP 440 compliant #42

vyasr opened this issue Mar 21, 2023 · 0 comments

Comments

@vyasr
Copy link
Contributor

vyasr commented Mar 21, 2023

In the long run all of our tooling will need to generate and consume PEP 440 compliant versions. Currently conda supports PEP 440 along with various extensions to the syntax for historical reasons (and in some cases, convenience), but that will eventually become untenable as wheel builds and pip packaging become more central to our workflows. Once dfg becomes a true single source of truth for versions, it would also make sense to add version linting as a validation step to ensure that all versions in dependencies.yaml are compliant. Version normalization is fairly easy to do by simply constructing a packaging.version.Version and ensuring that the string representations have not changed (there may also be a helper function to check this directly).

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

1 participant