On Sun, Apr 20, 2014 at 2:42 AM, Antoine Pitrou wrote:
> On Sat, 19 Apr 2014 19:02:42 -0700
> David Aguilar wrote:
>>
>> On python3, this still works for normal platforms, but on windows we
>> can't pass a list of byte strings. We have to pass a list of unicode
>> strings.
>
> Windows native APIs
On Sat, 19 Apr 2014 19:02:42 -0700
David Aguilar wrote:
>
> On python3, this still works for normal platforms, but on windows we
> can't pass a list of byte strings. We have to pass a list of unicode
> strings.
Windows native APIs are unicode-based. It is actually necessary to pass
*unicode* str
On Python 3, you can use Unicode on all platforms. On UNIX, there is no
need to encode explicitly.
Victor
Le 20 avr. 2014 04:17, "David Aguilar" a écrit :
> Hi,
>
> I just joined python-dev because I found the need to add some code to
> paper over python3's subprocess API, and I'm wondering whet
Hi,
I just joined python-dev because I found the need to add some code to
paper over python3's subprocess API, and I'm wondering whether I'm
missing something.
On python2 and python3, the (only?) way to get utf-8 arguments to
subprocess was to ensure that all unicode strings are encoded into
byte
