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
What's the problem this feature will solve?
Test PyPI is intended for testing Python packaging. Great, but there is a fatal flaw - the very newbie you target can easily make mistakes before learning about no filename reuse (e.g. me). Now they have to maintain two separate packages, one renamed for testing and second for live - this is asking for trouble.
Describe the solution you'd like
Provide some means of removing all records of a package name from Test PyPI, with a clear warning that this would not be possible in live PyPI. Nuking and restarting should be acceptable when testing.
The text was updated successfully, but these errors were encountered:
PyPI does not allow for a filename to be reused, even once a project has been deleted and recreated. To avoid this situation, use Test PyPI to perform and check your upload first, before uploading to pypi.org.
PyPI does not allow for a filename to be reused, even once a project has been deleted and recreated. To avoid this situation, use Test PyPI to perform and check your upload first, before uploading to pypi.org.
So I would have thought that Test PyPI would allow you to test package uploading and, thus, wouldn't complain if you upload a package twice. But it does.
Is there a way to override this behaviour, i.e., have Test PyPI let you upload a package with the same name twice?
What's the problem this feature will solve?
Test PyPI is intended for testing Python packaging. Great, but there is a fatal flaw - the very newbie you target can easily make mistakes before learning about no filename reuse (e.g. me). Now they have to maintain two separate packages, one renamed for testing and second for live - this is asking for trouble.
Describe the solution you'd like
Provide some means of removing all records of a package name from Test PyPI, with a clear warning that this would not be possible in live PyPI. Nuking and restarting should be acceptable when testing.
The text was updated successfully, but these errors were encountered: