# Python \< restriction of limited api extension

**URL:** <https://discuss.python.org/t/python-restriction-of-limited-api-extension/80176>\
**Category:** Packaging\
**Created:** [February 10, 2025, 1:23pm UTC](https://discuss.python.org/t/python-restriction-of-limited-api-extension/80176 "2025-02-10T13:23:12Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![replabrobin](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/replabrobin/32/8686_2.png) [@replabrobin](https://discuss.python.org/u/replabrobin)\
**Post date:** [February 10, 2025, 2:21pm UTC](https://discuss.python.org/t/python-restriction-of-limited-api-extension/80176/3 "2025-02-10T14:21:51Z")

</div>

I asked here about the issue here

> [@C stable api PY\_SSIZE\_T\_CLEAN error](https://discuss.python.org/t/c-stable-api-py-ssize-t-clean-error/80159):
>
> I maintain an optional reportlab c extension [rl-accel · PyPI](https://pypi.org/project/rl-accel/) It has been working fine in Python 3.7 - 3.12 when compiled as a stable api 3.7 extension. Problems were observed using this in 3.13 and 3.14 and I was advised that changes had made some commen macros behave differently. Compiling with a later python would improve things although speed might be reduced. I now observe the following error when using a Python 3.14/3.13 compiled extension with python \<=3.12 File “/home/robin/devel/re…

I looked at the sources of 3.12.9 and 3.13.2 and see that PY\_SSIZE\_T\_CLEAN seems to have no usage at all in the 3.13 code. So there’s no obvious way to allow `PyArg_ParseTuple` to work across the 3.12 - 3.13 boundary if compiled in 3.13. If I compile in \<3.13 I see other errors related to refcounts etc in 3.13/3.14.

---

_[View the full topic](https://discuss.python.org/t/python-restriction-of-limited-api-extension/80176)._