Repository navigation
✨ feat(py_info): expose marker environment - #178
Merged
gaborbernat merged 2 commits intoOct 30, 2026
Merged
Conversation
gaborbernat
marked this pull request as draft
October 30, 2026 19:49
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
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.
A tox issue shows a lock file selecting a package for the host Python when the discovered target has different marker values. Consumers need the target's complete default marker environment; tox's current fix obtains it with another interpreter query. This PR makes those values available from the discovery result.
The existing interpreter probe records all 11 default marker values in the target process.
PythonInfocarries them through its existing JSON and disk cache serialization. Parity tests usepackaging; production adds no runtime dependency.Validation
Linux 3.9: 660 passed, 16 skipped; Linux 3.15: 658 passed, 17 skipped. Both report 100% coverage. Type checks for 3.9 and 3.15, docs with warnings treated as errors, and prek pass.
All four new marker tests pass on Windows 3.11 and 3.15, including platform values changed inside the target process. The full Windows 3.15 suite has 18 failures in existing discovery and registry tests; unmodified 1.7.0 reproduces the same 18 test IDs.