# Feedback on abstract for pyconfr? Universal Python extensions

**URL:** <https://discuss.python.org/t/feedback-on-abstract-for-pyconfr-universal-python-extensions/98324>\
**Category:** Python Help\
**Created:** [July 10, 2025, 3:01pm UTC](https://discuss.python.org/t/feedback-on-abstract-for-pyconfr-universal-python-extensions/98324 "2025-07-10T15:01:46Z")\
**Posts on this page:** 1\
**Showing post:** 30

<div class="post-metadata">

**Author:** ![ncoghlan](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ncoghlan/32/14266_2.png) [@ncoghlan](https://discuss.python.org/u/ncoghlan)\
**Post date:** [July 15, 2025, 2:14am UTC](https://discuss.python.org/t/feedback-on-abstract-for-pyconfr-universal-python-extensions/98324/30 "2025-07-15T02:14:09Z")

</div>

The immediate motivation for sorting out an updated stable ABI is the free threaded builds: [Stable ABI/Limited API for free-threaded builds](https://discuss.python.org/t/stable-abi-limited-api-for-free-threaded-builds/86458/)

That isn’t a transition to a full handle API, but it does involve making object layouts opaque, which is at least friendlier to having the API pointer values represent object handles instead of object instances.

---

_[View the full topic](https://discuss.python.org/t/feedback-on-abstract-for-pyconfr-universal-python-extensions/98324)._