FEAT: Nightly dev wheel

[pllim]

Since this package has C-extension, might be nice to have a nightly dev wheel uploaded like astropy, so downstream packages (e.g., acstools, jdaviz) do not have to build photutils from source for their devdeps jobs.

Maybe a simpler version of https://github.com/astropy/astropy/blob/main/.github/workflows/publish.yml

Will need @astrofrog's help to set up the upload destination. 🙏

[bsipocz]

I would strongly advocate for an openastronomy destination, that could host astropy, sunpy, pyerfa, photutils, regions, etc.

x-ref: cc @nabobalis and scientific-python/upload-nightly-action#50

(and would advocate reusing the SP upload action (once the pending PR, that would support an alternative upload location, is merged), as we do keep maintaining that for the core SP library wheels)

[pllim]

astropy (and pyerfa) already has an established and advertised location, so I probably won't move that. But other packages downstream sharing a space will be nice, if quota isn't an issue.

[bsipocz]

astropy (and pyerfa) already has an established and advertised location

that can also still nicely changed. As the pyerfa stuff is still not at all trivial or intuitive (and got used more widely only in the past month or so)

[pllim]

Re: astropy and/or pyerfa -- If it can have redirect, would be nice. Otherwise, will have to carefully plan the transition. Also pyerfa is technically not part of Astropy (it is upstream, so need to ask pyerfa devs).

[bsipocz]

pyerfa is technically not part of Astropy

Thus the "openastronomy" umbrella. As in practice as an astropy downstream user we only need the pyerfa wheel as astropy is otherwise incompatible, we have absolutely no direct or indirect usage of it.

[pllim]

Let me ping pyerfa (https://github.com/liberfa/pyerfa) devs: @avalentino @mhvk @astrofrog

[mhvk]

Definitely a good idea to have all the packages in a single location! (Though easy to say as I'm not sure how to actually do it...)