Repository navigation
Conversation
…etails.json With --with-build-python, the build Python can differ from the target in patch version or release serial, but version_info and hexversion came from the running interpreter. Read them from Include/patchlevel.h instead, falling back to sys.version_info when the header is not there. Co-Authored-By: Claude Fable 5.1 <[email protected]>
itamaro
added
build
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.
With
--with-build-python, the build Python can differ from the target in patch version or release serial, butlanguage.version_info,implementation.versionandimplementation.hexversioncame from the running interpreter. This reads them fromInclude/patchlevel.h, the same way the Doc build does, with a fallback tosys.version_infowhen the header is not there.Written with assistance from Claude Fable 5.1