PR: Rename signatures module to array_api

[steff456]

This PR,

• Rename the signatures module to array_api
• Add imports in the __init__.py to provide a flat namespace of all the core modules (extensions are not included)

With these changes I'm still not able to use the flat namespace name in the references when rendering with sphinx, but it should work if you are importing the module from your documentation @leofang. Please let me know if it works!

Fixes #428

[leofang]

Thanks, Stephannie! That's quick. Let me try the patch locally later tonight.

[leofang]

Hi @steff456 and all, I hope you don't mind, I just pushed 9a25cdf to make sure the flattened namespace is accessible by intersphinx. The fact that with this change our own documentation is also using the flattened namespace means that we're testing it ourselves before publishing. A command line check is this:

$ python -m sphinx.ext.intersphinx _build/html/objects.inv

It should list what functions, attributes, etc are accessible to intersphinx and their corresponding hyperlinks.

[leofang]

Not sure why but the CI hits a permission issue...?

[leofang]

Not sure why but the CI hits a permission issue...?

Ah OK, I also hit this issue before. It's because this GH action dislikes PRs from forking branches... I think this is ready for review.

[asmeurer]

This can also be useful for verifying this https://github.com/bskinn/sphobjinv

[leofang]

@asmeurer @honno Will the changes here impact the test suite?

[asmeurer]

Yeah they will, but that shouldn't block the merging here. We pin the array-api repo with a submodule so we can update it independently.

[leofang]

Giving my 👍 despite I also worked on this PR 🙂

[kgryte]

LGTM. Thanks, @steff456, @leofang, @honno. Let's get this in, and try it out.

I updated the PR to follow @honno's suggestion of importing data_types as dtype. Hence, @leofang you'll want to document against dtype.__eq__.

[leofang]

Thanks, everyone!

[leofang]

Continue the discussion back in the original issue #428.