Rename package

[nstarman]

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

numpy has a policy that non-numpy-affiliated packages aren't called numpy. While they can't police it, they do ask everyone not to be rude.
In a similar vein, camping on array_api is rude.

Describe alternatives you've considered

None.

Additional context

No response

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.

[nstarman]

Cross-posting from data-apis/array-api-typing#14 (comment)

@34j We'd be very happy to take a PR adding in the very-useful automatic code generation, although your work in https://github.com/34j/array-api/tree/main/src/array_api_compat might be best done as an official array-api-compat-stubs package! Something to consider.

[34j]

The package name was available and I thought it was okay. Usually if you want to avoid such a thing, you reserve the name by uploading an empty package beforehand.

[34j]

Oh you mean the module name?

[nstarman]

I mean the name PyPI package array_api.
I'm actually not any "official" type member of the Array API consortium, just an interested party who contributed time and effort and volunteered more time to help with the typing work.
So to address "Usually if you want to avoid such a thing, you reserve the name by uploading an empty package beforehand." I agree! Unfortunately I can't do that because then I would be making the same problem as here.

I do have https://pypi.org/project/array-api-jax-compat/, but anyone who wants it can have it! I renamed it to quaxed to avoid this problem and kept the pypi only for forwarding.

[nstarman]

Linking back to here: #6 (comment)

I would not recommend abandoning this good work, just making a more concerted effort to engage with the community. You'll find them friendly, by and large. This package would serve as a good base for a array-api-compat-stubs package and perhaps an official part of the array-api consortium. (I can't make that determination, see #6 (comment)). Both this and the developing array-api-typing would benefit from the cross-talk. Some aspects of this repo could move to array-api-typing (let's discuss), which aims only to support the core Array API, and not to offer stubs for the broader ecosystem, like array-api-compat.