Skip to content

Conversation

zklaus
Copy link
Contributor

@zklaus zklaus commented Sep 23, 2025

  • Change is either:
    • To a Draft PEP
    • To an Accepted or Final PEP, with Steering Council approval
    • To fix an editorial issue (markup, typo, link, header, etc)
  • PR title prefixed with PEP number (e.g. PEP 123: Summary of changes)

This PR updates PEP 780 to make use of the new sys.abi_info namespace that stems from the original PEP 780 discussion.

Pinging @rgommers, @lysnikolaou.


📚 Documentation preview 📚: https://pep-previews--4608.org.readthedocs.build/

@zklaus zklaus requested a review from lysnikolaou as a code owner September 23, 2025 16:05
Copy link
Contributor

@rgommers rgommers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @zklaus! On reflection, I think I like the name::value syntax, it seems better than using things like sys_abi_info_free_threaded as boolean markers.

Only two minor comments from me.

significant period of time, it looked likely that support would first be
added in a fork. There are a lot of projects that depend on ``cffi``, which
are likely fine to start depending on a fork for free-threading only, however
depending on a fork for >=3.13 or for all Python versions seems like a much
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
depending on a fork for >=3.13 or for all Python versions seems like a much
depending on a fork for >=3.13 or for all Python versions seemed like a much

Comment on lines +220 to +221
- ``{'free_threaded::True', 'pointer_bits::64'}``,
``{'free_threaded::False', 'debug::True', 'pointer_bits::32'}``
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be useful to add endianness to illustrate if string values are quoted or not under the new :: scheme?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants