➜

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 davispuh
Recipients davispuh, eryksun, ezio.melotti, martin.panter, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2016-09-03.21:21:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1472937717.21.0.508045513808.issue27179@psf.upfronthosting.co.za>
In-reply-to
Content 
That is a great PIP, but it will take a lot of time to be implemented and it doesn't really solve this issue.

This is different issue than filename/path encoding. Here we need to decode binary output from other applications and that for a lot of applications will be console's code page but it could be also any other. This isn't issue about Unicode paths because application which is located at ASCII path, when we run it as a subprocess can return text output in console's code page, OEM, ANSI or some other encoding.

My proposed subprocess_fix_encoding_v4fixed.patch fixes this for majority of cases and for other cases encoding can be specified.
History
Date User Action Args
2016-09-03 21:21:57davispuhsetrecipients: + davispuh, paul.moore, vstinner, tim.golden, ezio.melotti, martin.panter, zach.ware, eryksun, steve.dower
2016-09-03 21:21:57davispuhsetmessageid: <1472937717.21.0.508045513808.issue27179@psf.upfronthosting.co.za>
2016-09-03 21:21:57davispuhlinkissue27179 messages
2016-09-03 21:21:56davispuhcreate