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 steve.dower
Recipients Ilya.Kulakov, christian.heimes, ezio.melotti, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2016-09-15.13:33:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473946396.32.0.534875064086.issue27354@psf.upfronthosting.co.za>
In-reply-to
Content
TESTFN_UNENCODABLE will be invalid utf8 now, as the name is chosen by attempting to encode a list of names and using the first one to fail.

No code pages have emoji in them AFAIK, so a test with one of those would do.

ISTR looking at this function though and finding that OpenSSL will decide utf8 if that's what is passed, in which case we're fine now. Or maybe I'm thinking of Tcl...
History
Date User Action Args
2016-09-15 13:33:16steve.dowersetrecipients: + steve.dower, paul.moore, vstinner, christian.heimes, tim.golden, ezio.melotti, zach.ware, Ilya.Kulakov
2016-09-15 13:33:16steve.dowersetmessageid: <1473946396.32.0.534875064086.issue27354@psf.upfronthosting.co.za>
2016-09-15 13:33:16steve.dowerlinkissue27354 messages
2016-09-15 13:33:16steve.dowercreate