Add the Python version to the API data.

[P403n1x87]

BPO	43931
Nosy	@miss-islington, @P403n1x87
PRs	bpo-43931: Export Python version as API data #25577

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2021-12-10.02:42:16.634>
created_at = <Date 2021-04-24.14:37:54.101>
labels = ['expert-C-API', 'type-feature', '3.10']
title = 'Add the Python version to the API data.'
updated_at = <Date 2021-12-10.02:42:16.633>
user = 'https://github.com/P403n1x87'

bugs.python.org fields:

activity = <Date 2021-12-10.02:42:16.633>
actor = 'pablogsal'
assignee = 'none'
closed = True
closed_date = <Date 2021-12-10.02:42:16.634>
closer = 'pablogsal'
components = ['C API']
creation = <Date 2021-04-24.14:37:54.101>
creator = 'Gabriele Tornetta'
dependencies = []
files = []
hgrepos = []
issue_num = 43931
keywords = ['patch']
message_count = 2.0
messages = ['391779', '408169']
nosy_count = 2.0
nosy_names = ['miss-islington', 'Gabriele Tornetta']
pr_nums = ['25577']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue43931'
versions = ['Python 3.10']

[P403n1x87]

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...).

[miss-islington]

New changeset 5066908 by Gabriele N. Tornetta in branch 'main':
bpo-43931: Export Python version as API data (GH-25577)
5066908