Switch to using an API upload token?

[ncoghlan]

Now that PyPI supports using API upload tokens for deployments, it would be nice to use that in this example.

Travis cover using an API token with their native deployment tooling here: https://docs.travis-ci.com/user/deployment/pypi/

The main API token docs are here: https://pypi.org/help/#apitoken

The minimalist update to the current example would be to:

1. Change the example username to __token__
2. Note that TWINE_PASSWORD needs to be set to the API token, rather than the user password

[joerick]

Hi @ncoghlan ! Thanks for the note! We've been tracking this over in pypa/cibuildwheel#154, too. I've been holding off on recommending this quite yet because I think the feature is still in beta, in case something changes. Is that still the case, or is this very likely to be stable from now on?

[ncoghlan]

My understanding is that the beta testing is going well, so incompatible changes are unlikely, but tagging @brainwane to ask if there is an ETA for the "beta" qualifier being dropped.

[brainwane]

Good question! pypi/warehouse#5661 (comment) is where I've been tracking what we need in order for the API token feature to emerge from beta. Right now there's a hard-to-understand error on the command line when users have a particular kind of credential problem pypi/warehouse#6232 , and I believe announcing the feature without fixing that would lead to a bunch of support requests and similar headaches. I've asked Warehouse developers to expedite fixing it so we can come out of beta.

[joerick]

Thanks @brainwane ! Looks like things are moving, I'll keep an eye on those threads

[joerick]

Done! Thank you both!

[ncoghlan]

Thank you for cibuildwheel!

[brainwane]

@joerick and @ncoghlan thanks for causing me to take a fresh look and re-nudge the beta features!