Message135756
| Author | vstinner |
|---|---|
| Recipients | Arfrever, alexis, benjamin.peterson, eric.araujo, georg.brandl, hagen, lemburg, mgorny, python-dev, tarek, vstinner |
| Date | 2011-05-10.23:06:21 |
| SpamBayes Score | 0.009701361 |
| Marked as misclassified | No |
| Message-id | <1305068782.01.0.494898072891.issue10419@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Issue fixed in Python 3.1, 3.2, 3.3. Thanks to Arfrever, I realized that this issue not only concerns the compilation of Python itself with a non-ASCII prefix (issue #6011), but the installation of any Python script containing a non-ASCII character. So I also fixed it in Python 3.1. I replaced os.fsencode(name) by name.encode(sys.getfilesystemencoding(), 'surrogateescape') in 3.1. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-05-10 23:06:22 | vstinner | set | recipients: + vstinner, lemburg, georg.brandl, benjamin.peterson, tarek, eric.araujo, hagen, Arfrever, alexis, mgorny, python-dev |
| 2011-05-10 23:06:22 | vstinner | set | messageid: <1305068782.01.0.494898072891.issue10419@psf.upfronthosting.co.za> |
| 2011-05-10 23:06:21 | vstinner | link | issue10419 messages |
| 2011-05-10 23:06:21 | vstinner | create | |