-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
METADATA.toml versions redux#2 #6095
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
Labels
project: policy
Organization of the typeshed project
Comments
To clarify: We allow two forms:
|
srittau
added a commit
to typeshed-internal/stub_uploader
that referenced
this issue
Sep 30, 2021
Versions are now free to have any number of dots Extract fetch_pypi_versions() from read_base_version() See python/typeshed#6095
srittau
added a commit
to typeshed-internal/stub_uploader
that referenced
this issue
Oct 7, 2021
Versions are now free to have any number of dots See python/typeshed#6095
srittau
added a commit
to srittau/typeshed
that referenced
this issue
Oct 7, 2021
This is a first step towards python#6095, where x.y and x.y.* are treated as equivalent. The next step is to update existing versions to use x.y.* where applicable and then treat x.y differently.
This was referenced Oct 7, 2021
srittau
added a commit
that referenced
this issue
Oct 10, 2021
This is a first step towards #6095, where x.y and x.y.* are treated as equivalent. The next step is to update existing versions to use x.y.* where applicable and then treat x.y differently. Co-authored-by: Akuli <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One practical problem with the current versioning scheme is that we can't correctly version the
dataclasses
stub. Current upstream version is 0.8. If we use0.8
as version, the tests try to installdataclasses==0.8.*
, which doesn't work. Similar problems would exist with calver or other exotic versioning schemes.Currently, the tests try to install
f"{distribution}=={version}.*
. I would suggest that we allow standard Python version range specifiers in the version field and change most existing versions to use e.g. "5.3.*". The tests would then be changed to simply installf"{distribution}=={version}"
. This would give us more flexibility.The text was updated successfully, but these errors were encountered: