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 simpkins
Recipients eric.araujo, giampaolo.rodola, janssen, pitrou, simpkins
Date 2011-08-25.05:43:27
SpamBayes Score 5.9868777e-12
Marked as misclassified No
Message-id <1314251008.43.0.367839411281.issue12803@psf.upfronthosting.co.za>
In-reply-to
Content
OpenSSL doesn't appear to do any special handling for i18n, and just
treats the strings as binary data.  It uses fgets() to read the password
from the terminal, so it will receive it however the terminal encodes
it.

It's not clear to me that PyUnicode_EncodeFSDefault() is quite the right
thing to do.  The initfsencoding() routine seems different from how
initstdio() works (which checks the PYTHONIOENCODING environment
variable, and then appears to fall back to os.device_encoding()).

I'm leaning towards just updating the docs to specify that if a string
is supplied it will be encoded using UTF-8.  I'm happy to do either way
you recommend, though.
History
Date User Action Args
2011-08-25 05:43:28simpkinssetrecipients: + simpkins, janssen, pitrou, giampaolo.rodola, eric.araujo
2011-08-25 05:43:28simpkinssetmessageid: <1314251008.43.0.367839411281.issue12803@psf.upfronthosting.co.za>
2011-08-25 05:43:27simpkinslinkissue12803 messages
2011-08-25 05:43:27simpkinscreate