Invalid or non-existent authentication information

[tylerlong]

When I run python setup.py sdist upload

I always get:

Submitting dist/xxxxxxx-0.1.4.tar.gz to https://upload.pypi.org/legacy/
Upload failed (403): Invalid or non-existent authentication information.
error: Upload failed (403): Invalid or non-existent authentication information.

It never asks me to enter my username but only password. So I assume the username is the same as when I run "register".

I am pretty sure that password I entered is correct because I can login https://pypi.python.org/pypi

Could you please help? I am not new to pypi. I published several packages before. But now I am confused. What has changed recently?

[tylerlong]

OK, I have got it done.

I turns out that I have to create ~/.pypirc

Entering password in terminal just doesn't work. It's very likely a bug. Because password is correct and it didn't give me chance to enter username.

[jaraco]

I was looking through this code recently. I think if there's no pypirc entry present, an empty username is used. The behavior exists upstream in distutils.

I did draft a change which would allow the username to default to getpass.getuser(), which is often a good default and which can be readily overridden with an environment variable.

I'll send a PR for review.

[dover247]

Heres What I Did To Fix:

Created ~/.pypirc File With The Following Contents:

[distutils]
index-servers =
    pypi

[pypi]
repository: https://pypi.python.org/pypi
username: <username>
password: <pass>

[seanbehan]

I ran into the same problem. I'm on a new OS X Sierra. Adding [server-login] entry to ~/.pypirc seemed to fix it http://www.seanbehan.com/how-to-fix-pypi-upload-failed-403-invalid-or-non-existent-authentication-information/

[jaraco]

@seanbehan: That [server-login] section is for old versions of Python (Python 2.5 and earlier if I recall correctly). Late versions still support this format, but I definitely recommend against it. Did you try the approach with the [distutils] section? Official docs are here.

[jaraco]

To the best of my knowledge, the behavior is working as expected.

[seanbehan]

@jaraco Thanks for the reply. I am using python 2.7 (homebrew python install on new mac book pro sierra) and the info from the docs you supplied does not work for me.

I have tried many variations and only [server-login] seems to work.

[koalalorenzo]

Same problem here, as well with homebrew on macOS Sierra

[tgalal]

same for me, python2.7 only [server-login] seems to work, everything results in asking for password at upload, and then auth problem. Although same config, unchanged, same upload command, unchanged, same python major version (2.7) used to work a few months a go with config format @dover247 suggests

[aphearin]

I just now attempted a new release and can report the exact same experience as @tgalal.

Thanks to @seanbehan for taking the time to post a workaround, which worked perfectly well for me.

[jaraco]

Well, the server-login workaround is a bad one, and it will probably break at some point. I wonder if this issue has emerged due to the fairly recent changes to support warehouse. Setuptools patches upload to use https://upload.pypi.org/legacy/ as the default repository (instead of https://pypi.python.org/pypi.

For what it's worth, I upload packages to PyPI at least weekly. I use the latest setuptools and Python and my pypirc looks like this:

[distutils]
index-servers =
    pypi

[pypi]
repository: https://upload.pypi.org/legacy/
username: jaraco

There's no password entry because I rely on the keyring support to resolve the password (and store it securely).

[seantrue]

@tgalal
The critical change for me was in @jaraco 's latest comment. I changed
repository: https://pypi.python.org/pypi to repository: https://upload.pypi.org/legacy/ and everything worked as promised.