Reconsider 3.11 support

[patrickhulce]

Is your feature request related to a problem? Please describe.

3.11 still has 2 more years before EOL and many organizations still rely on even older python.

Describe alternatives you've considered

Forking.

Additional context

Love what you've done here and would love to use it, thanks for making python better :)

Code of Conduct

• I agree to follow this project's Code of Conduct

Are you willing to resolve this issue by submitting a Pull Request?

• Yes, I have the time, and I know how to start.
• Yes, I have the time, but I don't know how to start. I would need guidance.
• No, I don't have the time, although I believe I could do it if I had the time...
• No, I don't have the time and I wouldn't even know how to start.

[34j]

Yes, I welcome any change requests to support 3.11

[34j]

I believe this approach can be implemented relatively easily. I would appreciate it if someone could submit a pull request.

#60 (comment)

import sys

if sys.version_info.minor < 12:
	class Meaningless
	    def __getitem__(*args):
			  pass
	Array = Meaningless

[patrickhulce]

I'm not sure I follow. The problem as I encountered it is that this library has adopted syntax for generics that was only introduced in 3.12. If we want those protocols to be runtime checkable and usable on earlier python versions, we'd need to revert that. Exposing a meaningless substitute type would not solve the problem I'm referring to.

FWIW, we've already forked and made all the necessary 3.11 changes manually but it would require commitment here to NOT keep adopting 3.12 features. Are you open to that?

[34j]

I apologize if my English wasn't clear, but maintaining the 3.12 syntax isn't a requirement—I simply don't have the energy to change the code myself. If you'd like to submit a PR, I'd gladly accept it. (I didn't expect users to be so concerned about 3.11 to be honest.) Since this project is already a "fork", I personally do not wish to see any further forks.

[34j]

Since the advantage of this repository over array-api-typing is that the types are auto-generated (data-apis/array-api-typing#23 (comment)), I do not want to accept direct change requests to _2022_12.py, ..., _draft.py. Please make it happen automatically, no matter how rudimentary the method may be.

(The types are generated by:

uvx --python 3.12 types-array-api[cli]

)

[patrickhulce]

Great thank you! I'll see if I get time for this in the next few weeks.