You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.
Given the user-specified project name matches the one used for PyPI deployments (which is the out-of-box setup, by the way) inadvertent name clashes are possible:
$ twine upload dist/*
Uploading distributions to https://upload.pypi.org/legacy/
Enter your username: ...
Enter your password:
Uploading ....whl
100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████| 10.7k/10.7k [00:01<00:00, 8.48kB/s]
HTTPError: 403 Client Error: The user '...' isn't allowed to upload to project '...'. See https://pypi.org/help/#project-name for more information. for url: https://upload.pypi.org/legacy/
Not sure if the proposal is relevant in terms of overall project roadmap though.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Given the user-specified project name matches the one used for PyPI deployments (which is the out-of-box setup, by the way) inadvertent name clashes are possible:
Not sure if the proposal is relevant in terms of overall project roadmap though.
The text was updated successfully, but these errors were encountered: