-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
suggest using API token when uploading to PyPI #343
Comments
I am not using API tokens myself yet, so I am not ready to recommend it. I do want to try it though. Thanks for pointing it out. I'll keep this issue open. |
I tried it out in one project: works like a charm. |
I am using a singe API token for all my projects. It works like a charm but it does not provide much more security than using the password. |
PyPI does support using different tokens for different projects; I presume you mean that you would like for zest.releaser to make it easier for you to use per-project tokens?
|
Why change, API tokens works exactly same way that user and password works. It's up to you: you can use token or credentials, official documentation is linked, you should use it for pypi configuration. |
Hi! In the documentation perhaps you could change
to instead suggest people use an API token for PyPI uploads?
Thanks!
The text was updated successfully, but these errors were encountered: