Using ABI instead of release version in site-packages path

[EwoutH (Ewout ter Hoeven)]

I just encountered this discussion and while not exactly the same problem as I was encountering, I think it does have some overlap and maybe a few similar roots or relevant ideas.

So for reference, if useful to anyone, two threads:

Create system to recognize, manage and install non-ABI-stable Python wheels (created with alpha/beta versions of Python)

I would like to open a discussion about recognizing, managing, distributing and installing non-ABI-stable Python wheels (a.k.a. wheels created with alpha/beta versions of Python), with the goal to speedup wheel deployment for new Python versions. In this topic start I will expand on the current situation and problem, propose potential solution and give some context. But I would mainly like to open a discussion on this topic. The current situation and problem Wheels are extremely important for…

From that discussion this specific idea was spun off:

Idea: Tracking ABI additions and changes for better pre-release wheel management

I would like to initiate a discussion on the idea of tracking ABI additions and changes in CPython, as suggested by Alyssa Coghlan (@ncoghlan) in a previous thread about recognizing, managing, and installing non-ABI-stable Python wheels created with alpha/beta versions of Python. Background The main issue is that wheels for new Python versions are often not immediately available, causing delays in the adoption of new Python features and improvements. This is due to the ABI’s potential to chang…