[Python][Packaging] Stop uploading nightly wheels to gemfury

[raulcd]

Describe the enhancement requested

Once we start uploading nightly wheels to the scientific python channel on anaconda:

• [Python] Uploading nightly wheels to the scientific python nightly channel #40216

we can drop uploading wheels to gemfury. We should also update any documentation about nightly wheels if any.

Component(s)

Packaging, Python

[jorisvandenbossche]

I think we should probably keep it for some time on both, and at least start with documenting the new index url as soon as possible.

(for example at least keep until 18.0 is released, when the stable docs will have the updated url)

[raulcd]

We don't seem to have updated the documentation on the new index URL, we should try update it for the next release.

[amoeba]

I filed an issue to document the new index URL, #45288, and just put up a patch for it, #45289. So the new text can land in Arrow 20.0.0.

Do we have any sense of whether Gemfury is being used at all? I'm not totally sure we'd have to wait until the release after 20.0.0 to remove Gemfury from CI considering how we present it to users. Either way, I'm happy to follow-up with a PR removing Gemfury after #45288 is resolved.

[jorisvandenbossche]

Do we have any sense of whether Gemfury is being used at all?

It is certainly being used by a bunch of projects to test the dev version of pyarrow. For example https://github.com/search?q=https%3A%2F%2Fpypi.fury.io%2Farrow-nightlies%2F&type=code

[amoeba]

Good call on doing that search. If we just stop uploading to gemfury and those projects don't migrate, I guess they'll think they're testing against a recent PyArrow nightly when they're actually just getting the last version we published to gemfury which could be very out of date. Maybe we can do the following:

1. Stop uploading nightly wheels to gemfury
2. Post to the dev list (using careful language to make it clear the nightlies aren't an official release, etc, etc)
3. Filter through that GitHub search and identify repos to file issues against to notify of the change and give them a cutoff date
4. Disable/delete or otherwise remove the arrow-nightlies index so installs against it fail. This would be done

Is that too much? If it sounds good, I can take on 1, 2, and 3 if someone with credentials can do 4 when the time comes.