Expand on using TestPyPI in the distributing guide

[theacodes]

Original context: #271 (comment)

We already mention that TestPyPI is an option, however, we link off to separate documentation on how to use it. We should self-host this documentation and better surface it in our guide.

[dstufft]

FWIW Longish term I want to get rid of TestPyPI, by folding it's primary use case as a baked in feature to Warehouse. Essentially by using pypi/warehouse#726 people can just upload a release without publishing it, then if they don't want to keep it they can just delete it.

[theacodes]

@dstufft what's the timeline on that (if any)? I just want to know how to prioritize this.

[dstufft]

It's lower priority work then getting legacy shut down and migrated, beyond that, whenever someone (or me) feels like working on it.

[theacodes]

Gotcha. :)

[theacodes]

I think this is sufficiently covered by #366 for now, and long-term a new tutorial for publishing packages can mention this.

[brainwane]

Now that we have https://packaging.python.org/guides/using-testpypi/ can we close this issue?

[theacodes]

Probably, and I can expand on this more when I get a chance to re-write the distributing guide.

…

On Tue, Mar 20, 2018 at 1:44 PM Sumana Harihareswara < ***@***.***> wrote: Now that we have https://packaging.python.org/guides/using-testpypi/ can we close this issue? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#298 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAPUc7KWcCJh-Nxhh_KxDBCn7Ge3AJ5xks5tgWo5gaJpZM4NCDE0> .