Allow PEP440 versions for python plugins #60137
Merged
+2
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Support alpha and beta version syntax from PEP440 for python plugins see https://peps.python.org/pep-0440/
T4mmi
force-pushed
the
Allow-PEP-versions-for-plugins
branch
from
50785de to
0b8652f
Compare
🪟 Windows buildsDownload Windows builds of this PR for testing. 🪟 Windows Qt6 buildsDownload Windows Qt6 builds of this PR for testing. |
m-kuhn
approved these changes
Jan 14, 2025
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Python allows for
1.0a1style version syntax instead of1.0.alpha1semver style.This PR works with
setuptools_scmsyntax, but does not fixes every PEP440 syntaxes:devversions are trickier to treat (but we might ignore them since these versions should not be uploaded on repos)0.1alpha1>0.1a2(but coventions should be consistent inside a project)