Add python interpreter info to uv workspace metadata#20502
Merged
Conversation
zanieb
reviewed
Jul 17, 2026
Comment on lines
+121
to
130
| /// Information about the Python interpreter in a synchronized environment. | ||
| #[derive(Debug, serde::Serialize)] | ||
| struct MetadataPython { | ||
| /// Absolute path to the Python executable. | ||
| path: PortablePathBuf, | ||
| /// Full Python version. | ||
| version: Version, | ||
| /// Python implementation name. | ||
| implementation: String, | ||
| } |
Member
There was a problem hiding this comment.
Can we share the type with the sync impl?
Contributor
Author
There was a problem hiding this comment.
Slightly gross because of the crates they're defined in but yeah it works.
Member
There was a problem hiding this comment.
We could add a new crate for it, long-term I think there should definitely be shared schemas
zanieb
reviewed
Jul 17, 2026
| /// Full Python version. | ||
| version: Version, | ||
| /// Python implementation name. | ||
| implementation: String, |
Member
There was a problem hiding this comment.
Why isn't this ImplementationName?
Contributor
Author
There was a problem hiding this comment.
The sync impl also used String but I've changed it to untagged LenientImplementationName which... is ultimately just String with extra steps.
Member
There was a problem hiding this comment.
The extra steps are what Rust is all about, rite?
zanieb
approved these changes
Jul 17, 2026
This should be the same format as `uv sync --format json`. Several times it's come up that ty might want this info spoon-fed to it and it's just generally nice to have, so let's add it. Intentionally no changes to the equivalent `uv tree` json because it doesn't do --sync.
Gankra
enabled auto-merge (squash)
July 20, 2026 14:24
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This should be the same format as
uv sync --format json. Several times it's come up that ty might want this info spoon-fed to it and it's just generally nice to have, so let's add it.Intentionally no changes to the equivalent
uv treejson because it doesn't do --sync.