twine should not fail silently about twine HOT 14 CLOSED

What file?

from twine.

In this case it was wheel.

from twine.

No I mean what project, version, filename on PyPI.

from twine.

pygments-q, 0.5, pygments_q-0.5-py2.py3-none-any.whl.

Note, that another owner was able to upload file without a problem.

from twine.

I see that file on https://pypi.python.org/pypi/pygments-q. Did you perhaps just check too soon before the Web UI cache was updated with the new version?

from twine.

It was uploaded from different project owner's account couple minutes later and it did show up there right away. For my username/password combination it silently failed. And I waited for 10-15 minutes for it to show up.

from twine.

Hmm. Strange. That would mean that PyPI accepted it but didn't save it somehow.

from twine.

Ok, I think I figured out what heppend:

1. I had wrong URL for repository. Instead of https://pypi.python.org/pypi I had https://www.python.org/pypi.
2. When you connect to https://www.python.org/pypi, you get 301 redirect to correct URL:

$ curl -I https://www.python.org/pypi
HTTP/1.1 301 Moved Permanently
Date: Fri, 30 Jan 2015 18:25:54 GMT
Server: nginx
Content-Type: text/html
Location: https://pypi.python.org/pypi?
...

Is this case supported?

from twine.

Ah. No it's not supported.

I wonder if we should get rid of that redirect.

from twine.

It's better to update Python documentation, which pointed me to wrong server ;-)

from twine.

But still, if it is not supported, you should say so somehow in the error message.

from twine.

So I toyed with raising an exception in the case of a redirect but I'm not exactly sure it's the best idea. It would be pretty simple so long as we bump the minimum version of requests. I don't think anyone is using twine for anything other than PyPI, so it should be a relatively reliable way of preventing this kind of confusion.

That said, a redirect to a different subdomain would cause requests to not attempt to post the body again, so the redirect like that won't ever be successful. I have pushed a branch with my rough approximation of what this would look like. https://github.com/pypa/twine/tree/bug/92

from twine.

I like your change - that would have saved me an hour or so of my time today. :)

from twine.

I just experienced this issue, and @sigmavirus24's fix proposal looks better than everything I've come up with <3

from twine.