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 drzraf
Recipients drzraf
Date 2012-05-17.21:23:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1337289825.27.0.400304162278.issue14844@psf.upfronthosting.co.za>
In-reply-to
Content
Accentuated characters are not accepted in password.
While it (unicode) was quickly talked about in issue557704 it appears that issue1170 aimed to solve this by making shlex unicode-compatible but it does not seem to be the case (at least with python 3.2 in the netrc use-case).

On a side note :
- a blank line between two comment lines
 and
- lines starting with a '#' *not* followed by a space
 fail too (shells supports both of them)
History
Date User Action Args
2012-05-17 21:23:45drzrafsetrecipients: + drzraf
2012-05-17 21:23:45drzrafsetmessageid: <1337289825.27.0.400304162278.issue14844@psf.upfronthosting.co.za>
2012-05-17 21:23:44drzraflinkissue14844 messages
2012-05-17 21:23:44drzrafcreate