Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plans to publish signatures to pypi? #411

Open
tlambert03 opened this issue Mar 26, 2022 · 5 comments · May be fixed by #472
Open

Plans to publish signatures to pypi? #411

tlambert03 opened this issue Mar 26, 2022 · 5 comments · May be fixed by #472
Labels
Tools Issue or pull request pertaining to tooling for authoring and managing this specification.

Comments

@tlambert03
Copy link

Hi 👋

love what's happening here.

I'm playing around with stubbing out protocols for common image analysis operations (e.g. scikit-image), and would love to build on what already exists in API_specification/signatures. I'm wondering if you have any plans to publish/distribute the stubs in that folder to PyPI?

@honno
Copy link
Member

honno commented Mar 27, 2022

I'd be interested in this for the test suite too, where we utilise signatures already. Might help us with data-apis/array-api-tests#107.

I imagine this could be a completely automated process from this repo (i.e. no separate repo), with calender versioned releases. Have to be mindful of #398—possibly the top-level package could be namespaced with each spec release, e.g. xp_signatures.v1. Probably worth waiting until we get a first spec release generally.

@rgommers
Copy link
Member

rgommers commented Aug 4, 2022

Probably worth waiting until we get a first spec release generally.

We now have a final release. This isn't too much work to do. Should we go ahead with this?

@honno
Copy link
Member

honno commented Aug 4, 2022

I'd propose we first work on setting up a workflow where the signatures folder is uploaded as-is, available at say the <pkg_name>.draft namespace. Then we could get onto uploading versioned namespaces, which might be a bit annoying but still quite do-able.

@kgryte
Copy link
Contributor

kgryte commented Apr 4, 2024

@honno Is this something that we can move forward?

@kgryte kgryte added the Tools Issue or pull request pertaining to tooling for authoring and managing this specification. label Apr 4, 2024
@kgryte kgryte changed the title plans to publish signatures to pypi? Plans to publish signatures to pypi? Apr 4, 2024
@honno
Copy link
Member

honno commented Apr 10, 2024

@honno Is this something that we can move forward?

I think we'd really want to get in #589 first (which LGTM but we'd want someone else to give the go-ahead, then we can ping nstarman to see if they can update/rebase the PR (or if not available I can have a go).

Then we could publish basically as-is, or I could update #472 with said changes assuming folks are happy with the direction I was going for... I'll have a think over but again #589 is blocking anywho IMO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Tools Issue or pull request pertaining to tooling for authoring and managing this specification.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants