bpo-43931: Export Python version as API data #25577
Open
+7
−0
Conversation
When Python is embedded in other applications, it is not easy to determine which version of Python is being used. This change exposes the Python version with the API data
P403n1x87
changed the title
|
Wouldn't it make more sense to export the hex version number? |
Yes it makes a lot of sense. Indeed I have thought about exporting something like as an alternative, which would certainly be more efficient to read and parse, but then I realised that I could do which is neat |
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.
When Python is embedded in other applications, it is not easy to determine which version of Python is being used. This change exposes the Python version as part of the API data. Tools like Austin (https://github.com/P403n1x87/austin) can benefit from this data when targeting applications like uWSGI, as the Python version can then be inferred systematically by looking at the exported symbols rather than relying on unreliable pattern matching or other hacks (like remote code execution etc...).
https://bugs.python.org/issue43931