How to upload to Pythonhosted.org

[waylan]

After asking here, I found a mailing list post here:
https://mail.python.org/pipermail/distutils-sig/2015-May/026381.html

That post outlines a roadmap for shutting down pythonhosted. Unfortunately, it
seems that they skipped from step 1 to step 5 without bothering with steps 2,
3, & 4.

In any event, that list discussion seems to be the official word that things
are being shut down, which was what I was looking for.  It's unfortunate that
things weren't done more smoothly.

Also it seems that if you want to avoid search results showing up for the
pythonhosted content after you find a new host, they at least provide a way to
"delete" the content from pyhtonhosted. That way, Google will stop indexing it
and stop including it in search results. Unfortunately, all the existing links
across the internet are now dead with no way to redirect people.

Waylan

On Thursday, November 30, 2017 at 1:47:32 PM UTC-5, Irmen de Jong wrote:
> On 11/30/2017 03:31 AM, Ben Finney wrote:
> > Irmen de Jong <irmen.NOSPAM at xs4all.nl> writes:
> >
> >> On 11/30/2017 02:06 AM, waylan wrote:
> >>> So, how do I upload an update to my documentation?
> >>
> >> I ran into the same issue. From what I gathered, Pythonhosted.org is
> >> in the process of being dismantled and it hasn't allowed new doc
> >> uploads for quite some time now. I switched to using readthedocs.io
> >> instead.
> >
> > The issue that many are facing is how to update the pages *at the
> > existing URL* to tell visitors where to go next. Cool URIs don't change
> > <URL:https://www.w3.org/Provider/Style/URI.html> but, when they do, we
> > are obliged to update the existing pages to point to the new ones.
>
> Sorry, yes, that is the problem I experience as well. My library's old
version
> documentation is somehow frozen on Pythonhosted.org (and obviously still pops
up as the
> first few google hits).
>
>
> > So, if pythonhosted.org is indeed being dismantled, there should be a
> > way to update the pages there for informing visitor where they should go
> > next.
> >
> > If that's not possible and instead the service is just locked down,
> > that's IMO a mistake.
>
> I agree with that. I think it's an unsolved issue until now, that gets some
discussion
> in this github issue https://github.com/pypa/warehouse/issues/582
>
>
> Irmen