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 joneskoo
Recipients carljm, ezio.melotti, jcea, joneskoo, maker, orsenthil, python-dev
Date 2012-01-14.12:10:40
SpamBayes Score 2.0273747e-08
Marked as misclassified No
Message-id <1326543041.79.0.297250222974.issue13642@psf.upfronthosting.co.za>
In-reply-to
Content
Updating the issue with version 3.2 tag since it was fixed there as well. Still fixed, of course.

You are correct that the encodings can be tricky. Luckily I only added coding to tests. But you're right, I would consider very carefully before using similar code outside tests.

I just realized what's the impact of this change on python3.2 really. Since urllib.request.urlopen (for some reason) does not allow username and password on the URI, it is not possible to hit this with that, I think. But FancyURLopener does allow using user-pass in url, so this bug was reachable. I just verified that and the fix :)

Fix does the trick for FancyURLopener when the username and password are passed in the URL.
History
Date User Action Args
2012-01-14 12:10:42joneskoosetrecipients: + joneskoo, jcea, orsenthil, carljm, ezio.melotti, maker, python-dev
2012-01-14 12:10:41joneskoosetmessageid: <1326543041.79.0.297250222974.issue13642@psf.upfronthosting.co.za>
2012-01-14 12:10:41joneskoolinkissue13642 messages
2012-01-14 12:10:40joneskoocreate