# Add \`sys.abi\_features\` to make information about the interpreter ABI more accessible

**URL:** <https://discuss.python.org/t/add-sys-abi-features-to-make-information-about-the-interpreter-abi-more-accessible/94422>\
**Category:** Core Development\
**Created:** [June 4, 2025, 11:52am UTC](https://discuss.python.org/t/add-sys-abi-features-to-make-information-about-the-interpreter-abi-more-accessible/94422 "2025-06-04T11:52:04Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![zklaus](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/zklaus/32/25923_2.png) [@zklaus](https://discuss.python.org/u/zklaus)\
**Post date:** [August 6, 2025, 4:56pm UTC](https://discuss.python.org/t/add-sys-abi-features-to-make-information-about-the-interpreter-abi-more-accessible/94422/10 "2025-08-06T16:56:54Z")

</div>

Thanks for the pointers, @encukou! Based on your suggestion, I came up with [an implementation for sys.abi\_info](https://github.com/python/cpython/pull/137476).

For now, I have only added the core three properties, though adding further ones is rather straight-forward.

Regarding the wheel next variants, I think it could be a good idea to align with this by declaring a special namespace, say `builtin`, `interpreter`, or, indeed, `abi_info`, which would allow us to refer to the pieces of abi information as, e.g. `builtin :: pointer_size :: 32` and similar for purposes of packaging.

---

_[View the full topic](https://discuss.python.org/t/add-sys-abi-features-to-make-information-about-the-interpreter-abi-more-accessible/94422)._
