Drop Python 3.10, and probably 3.11?

[NeilGirdhar]

Scipy has already dropped 3.10, so I assume we can here? Also, judging by the progress on this repo, it's unlikely there will be a 1.0 release for October when I imagine scipy will drop 3.11. So, might as well also drop 3.11?

[ntessore]

I have no stake in this, but why drop support for versions that can be supported with little or no effort?

[jorenham]

dropping 3.11 would allow us to use PEP 695 syntax

[ntessore]

I see. I think a low-level provider library like this one here should strive to support as many old and even unsupported Python versions as humanly possible, because every version you drop at the top of the dependency chain ripples all the way down to the bottom, and ultimately end users.

Case in point, we just had to remove Python 3.10 support in glass-dev/glass#1093 for no other reason than array-api-extra dropping Python 3.10 support, and it's caused real pain for a small number of users. Python versions unfortunately have a very long tail in science.

[lucascolley]

array-api-extra has been following scikit-learn's lead on supported Python versions. If GLASS were to decide on a policy that is more conservative than sklearn going forward, I would be happy in principle for array-api-extra to follow and provide that support.

I am still hoping for scientific-python/specs#389 to materialise to give us a standardised longer support window than SPEC 0 as is.

---

Now for array-api-typing, given the early stage of development, I think it would be best to get off the ground using any features of recent Python versions that ease the process — that could be followed by work on backporting to older versions once there is a push for adoption.

[NeilGirdhar]

I am still hoping for scientific-python/specs#389 to materialise to give us a standardised longer support window than SPEC 0 as is.

SPEC 0 LTS (plus one year) aligns with what I was suggesting in the issue: Drop 3.10 now and drop 3.11 in October (which essentially means that you can drop both now since this project won't release until October).

dropping Python 3.10 support, and it's caused real pain for a small number of users.

In what way? And why do they need the newest features of your library, but aren't able to upgrade Python?