Message388805
The complexity of mixing standard I/O from the shell and external programs is a limitation of the Windows command line. Each program could choose to use the system (or process) ANSI or OEM code page, the console session's input or output code page, UTF-8, or UTF-16. There's no uniform way to enforce one, consistent choice. So I'm closing this issue as a third party limitation that cannot be addressed in general. The problem has to be handled on a case by case basis. |
|
Date |
User |
Action |
Args |
2021-03-16 03:46:03 | eryksun | set | recipients:
+ eryksun, paul.moore, vstinner, giampaolo.rodola, tim.golden, zach.ware, steve.dower, Yoni Rozenshein |
2021-03-16 03:46:03 | eryksun | set | messageid: <1615866363.31.0.737633177378.issue33780@roundup.psfhosted.org> |
2021-03-16 03:46:03 | eryksun | link | issue33780 messages |
2021-03-16 03:46:02 | eryksun | create | |
|