Message276534
| Author | vstinner |
|---|---|
| Recipients | Ilya.Kulakov, christian.heimes, ezio.melotti, paul.moore, steve.dower, tim.golden, vstinner, zach.ware |
| Date | 2016-09-15.08:49:31 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1473929371.72.0.0718975181789.issue27354@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> Is this still an issue? I'm not 100% sure that SSL_CTX_load_verify_locations() accepts a path encoded to UTF-8 on Windows. To be 100% sure, it's "simple": try a filename not encoded to the ANSI code page on Windows. The best would be to have an unit test for that. You use use test.support.TESTFN_UNENCODABLE for example. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-09-15 08:49:31 | vstinner | set | recipients: + vstinner, paul.moore, christian.heimes, tim.golden, ezio.melotti, zach.ware, steve.dower, Ilya.Kulakov |
| 2016-09-15 08:49:31 | vstinner | set | messageid: <1473929371.72.0.0718975181789.issue27354@psf.upfronthosting.co.za> |
| 2016-09-15 08:49:31 | vstinner | link | issue27354 messages |
| 2016-09-15 08:49:31 | vstinner | create | |