# Python ABIs and PEP 703

**URL:** <https://discuss.python.org/t/python-abis-and-pep-703/34018>\
**Category:** Core Development\
**Created:** [September 18, 2023, 2:59pm UTC](https://discuss.python.org/t/python-abis-and-pep-703/34018 "2023-09-18T14:59:39Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![pf\_moore](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pf_moore/32/35_2.png) [@pf\_moore](https://discuss.python.org/u/pf_moore)\
**Post date:** [September 19, 2023, 2:12pm UTC](https://discuss.python.org/t/python-abis-and-pep-703/34018/14 "2023-09-19T14:12:00Z")

</div>

> [@colesbury](#):
>
> I don’t think we should worry too much about whether old versions of pip work properly for the _experimental_, `--disable-gil` build of CPython 3.13. As it is, old versions of pip frequently do not work with new versions of Python. For example, `pip==23.1.1` and older (from just 5 months ago) will break if installed in CPython 3.13 (missing pkgutil.ImpImporter).

Pip’s policy is that you should always upgrade to the latest version. I think it’s fine if an older version _breaks_ for newer Python. But I’m less sure that silently installing the wrong package is acceptable. People do use older versions of pip, and loud breakages aren’t the same as silent errors. But we (pip) don’t have a specific policy on this.

I don’t personally have a strong opinion on this, but I do think that if we want people to try out the free-threaded builds, having to debug ABI compatibility issues like this is likely to be rather off-putting for them.

---

_[View the full topic](https://discuss.python.org/t/python-abis-and-pep-703/34018)._