Tommy Carpenter added the comment:
Hi,
I think option B might be best, because the issue was that I didn't know at
first that the problem was in my .pypirc. I think this stack trace is not the
most elegant way for the user to figure that out. Maybe catching this and then
presenting a human
New submission from Tommy Carpenter:
Full details and stacktrace are at:
http://stackoverflow.com/questions/43001446/python-pypi-configparser-blowing-up-when-pointing-to-certain-repo/43001770#43001770
Essentially, I had an index-servers section that listed a repo, that was not
listed
