➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients alexis, eric.araujo, jaraco, tarek
Date 2011-09-13.15:20:01
SpamBayes Score 1.6777618e-05
Marked as misclassified No
Message-id <1315927203.67.0.106067628316.issue11473@psf.upfronthosting.co.za>
In-reply-to
Content 
This is a strange bug.  I added a test using -r server2, using the already-existing PYPIRC_LONG_PASSWORD string as .pypirc contents.  The test passes.  To make sure changing one test would not affect another one, I created a new .pypirc file, PYPIRC_CUSTOM_SERVER, and then I got to see your bug!  I tried various combinations of keys (realm or not, user or not), changed the markup (: or = as delimiter, spaces or not) but could not easily find the root of the bug.

Can you publish a .pypirc file that works with 2.7 and not with 3.2?  That would be a good starting point.
History
Date User Action Args
2011-09-13 15:20:03eric.araujosetrecipients: + eric.araujo, jaraco, tarek, alexis
2011-09-13 15:20:03eric.araujosetmessageid: <1315927203.67.0.106067628316.issue11473@psf.upfronthosting.co.za>
2011-09-13 15:20:02eric.araujolinkissue11473 messages
2011-09-13 15:20:02eric.araujocreate