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
Upload of existing packages is treated as success #354
Comments
What versions of twine, setuptools, pkginfo, and wheel are installed? Thanks! |
Right, sorry: setuptools==28.8.0 |
This is behaving as expected. What's happening here is that you're uploading the exact same file (same hash, same source, same filename, etc.) and there's just nothing for PyPI to do, since what you've requested (make this file the distribution for this version of this project) is already done. There's no problem with asking PyPI to do it again, because it would make no difference if PyPI did it again or not. Relevant issue that introduced this behavior is here: pypi/warehouse#2284 It's possible that you're experiencing a common user problem (hard to tell without more details), in which you've:
Usually this manifests itself as "I published a new distribution to PyPI but it's not showing up!" however in your case, it would be equivalent to the behavior you're seeing. |
Got it. I was indeed uploading the exact same file as part of a unit test, changed the test to modify the source code between executions and it worked as expected. Thanks for the clarification and quick response 👍 |
Glad we could help! :D Great work troubleshooting, @di. 🎉 |
Any chance something is broken in the way twine (or pypi) handles uploads of existing packages?
Case in point:
Running the same command should have resulted in a "File already exists" error, but now for some reason it just acts as if the package doesn't exist and prints the same output as the first execution. However, the actual package in pypi isn't overridden (which is good obviously).
Whats going on? Am i missing something? tested both on test.pypi and pypi... :\
Thanks
The text was updated successfully, but these errors were encountered: