Skip to content

Sync latest Python releases#18958

Merged
zanieb merged 1 commit intomainfrom
sync-python-releases
Apr 16, 2026
Merged

Sync latest Python releases#18958
zanieb merged 1 commit intomainfrom
sync-python-releases

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Automated update for Python releases.

@zanieb zanieb force-pushed the sync-python-releases branch from f5aadff to 954a97a Compare April 10, 2026 00:45
@zanieb zanieb marked this pull request as ready for review April 10, 2026 00:45
@zanieb zanieb enabled auto-merge (squash) April 10, 2026 00:45
@zanieb zanieb disabled auto-merge April 10, 2026 00:45
Comment thread crates/uv-python/download-metadata.json Outdated
Comment on lines +12628 to +12631
"url": "https://github.com/pyodide/pyodide/releases/download/314.0.0a1/xbuildenv-314.0.0a1.tar.bz2",
"sha256": null,
"variant": null,
"build": "314.0.0a1"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hoodmane I'm a bit confused by the discrepancy

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We're changing our versioning, if that is what you are referring to.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, the build is 314.0.0a1 but the CPython version is 3.14.2?

I'm also not sure what to do with pre-release build tags, that's not a concept we support today.

Can you explain the new versioning scheme perhaps?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the prerelease pyodide versions should be ignored by uv, I don't see any reason that uv should allow installing them.

The idea with the new versioning scheme was that we would put Python majorminor as the major version and then we increment the minor version when we do main branch releases and the patch version when we do backports. We haven't made a stable release following this convention yet so if you think that it is a really bad idea we could still change it if there is a compelling enough reason.

zaniebot pushed a commit to zaniebot/uv that referenced this pull request Apr 10, 2026
`PyodideFinder` was reading every release from the GitHub API, including
prereleases. Pyodide's `pyodide-cross-build-environments.json` only
exposes a `python_version` string with no prerelease marker, so an alpha
release like `314.0.0a1` was emitted as if it targeted stable CPython
3.14.2 — the generated entry's `prerelease` field was `""` while its
`build` field was `314.0.0a1`, which is the discrepancy surfaced on
astral-sh#18958.

Filter releases on `release["prerelease"]` so Pyodide alphas/betas are
ignored, matching the implicit stable-only policy of the other finders.

https://claude.ai/code/session_014joASNw6BxUAgDVxsnPZFj
@zanieb zanieb added the do-not-merge Pull request is not ready to merge label Apr 10, 2026
@github-actions github-actions Bot force-pushed the sync-python-releases branch 6 times, most recently from 5c2456e to 832a7cb Compare April 16, 2026 00:47
@zanieb zanieb removed the do-not-merge Pull request is not ready to merge label Apr 16, 2026
@zanieb zanieb enabled auto-merge (squash) April 16, 2026 04:16
@zanieb zanieb force-pushed the sync-python-releases branch from 832a7cb to 697b008 Compare April 16, 2026 04:16
@zanieb zanieb merged commit 8736c7b into main Apr 16, 2026
54 checks passed
@zanieb zanieb deleted the sync-python-releases branch April 16, 2026 04:28
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

Successfully merging this pull request may close these issues.

2 participants