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

[EwoutH (Ewout ter Hoeven)]

After more than a full year, the idea for tracking ABI additions and changes didn’t move forward at all. So I think we’re back to square one, which is this discussion: How can we create a system to manage non-ABI-stable Python wheels.

I did a new write up of the situation from my perspective here:

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

Thanks for getting back Brett. Let’s take a step back here. The goal is to provide the long dependency chain of libraries with more time to get their affairs in order during the pre-release phase of a new beta Python version. Many libraries can’t start testing because their testing and CI workflows require certain dependencies. However, often these dependencies are not built from scratch, but installed from wheels, to keep CI time and complexity in check. Especially scientific and geospatial pa…