John Nagle wrote:
> The problem is that only the NT-derived Microsoft systems
> talk Unicode. The DOS/Win16/Win9x family did not. But they did
> have CreateProcess. So the current code will handle Win9x, but not
> Unicode.
Please explain, I don't understand. If you try using Windows system
functio
Diez B. Roggisch wrote:
> Brian Smith wrote:
>
>> Diez B. Roggisch wrote:
>>> Sure thing, python will just magically convert unicode to the
>>> encoding the program YOU invoke will expect. Right after we
>>> introduced the
>>>
>>> solve_my_problem()
>>>
>>> built-in-function. Any other wishes?
>>
Diez B. Roggisch wrote:
> John Nagle wrote:
>
>> Benjamin wrote:
>>> On Jan 14, 6:26 pm, Bjoern Schliessmann >> [EMAIL PROTECTED]> wrote:
John Nagle wrote:
> It turns out that the strings in the "env" parameter have to be
> ASCII, not Unicode, even though Windows fully supports Unicod
Brian Smith wrote:
> popen() knows that it is running on Windows, and it knows what
> encoding Windows needs for its environment (it's either UCS2 or
> UTF-16 for most Windows APIs). At least when it receives a unicode
> string, it has enough information to apply the conversion
> automatically, and
Brian Smith wrote:
> Diez B. Roggisch wrote:
>> Sure thing, python will just magically convert unicode to the
>> encoding the program YOU invoke will expect. Right after we
>> introduced the
>>
>> solve_my_problem()
>>
>> built-in-function. Any other wishes?
>
> There's no reason to be rude.
I
Diez B. Roggisch wrote:
> Sure thing, python will just magically convert unicode to the
> encoding the program YOU invoke will expect. Right after we
> introduced the
>
> solve_my_problem()
>
> built-in-function. Any other wishes?
There's no reason to be rude.
Anyway, at least on Windows it m
John Nagle wrote:
> Benjamin wrote:
>> On Jan 14, 6:26 pm, Bjoern Schliessmann > [EMAIL PROTECTED]> wrote:
>>> John Nagle wrote:
It turns out that the strings in the "env" parameter have to be
ASCII, not Unicode, even though Windows fully supports Unicode in
CreateProcess.
That's o
Benjamin wrote:
> On Jan 14, 6:26 pm, Bjoern Schliessmann [EMAIL PROTECTED]> wrote:
>> John Nagle wrote:
>>> It turns out that the strings in the "env" parameter have to be
>>> ASCII, not Unicode, even though Windows fully supports Unicode in
>>> CreateProcess.
>> Are you sure it supports Unicode,
On Jan 14, 6:26 pm, John Nagle <[EMAIL PROTECTED]> wrote:
> I passed a dict for the "env" variable to Popen with Unicode strings
> for the dictionary values.
>
> Got:
>
>File "D:\Python24\lib\subprocess.py", line 706, in _execute_child
> TypeError: environment can only contain s
On Jan 14, 6:26 pm, Bjoern Schliessmann wrote:
> John Nagle wrote:
> > It turns out that the strings in the "env" parameter have to be
> > ASCII, not Unicode, even though Windows fully supports Unicode in
> > CreateProcess.
>
> Are you sure it supports Unicode, not UTF8 or UTF16? Probably using
>
John Nagle wrote:
> It turns out that the strings in the "env" parameter have to be
> ASCII, not Unicode, even though Windows fully supports Unicode in
> CreateProcess.
Are you sure it supports Unicode, not UTF8 or UTF16? Probably using
something like u"thestring".encode("utf16") will help.
Rega
I passed a dict for the "env" variable to Popen with Unicode strings
for the dictionary values.
Got:
File "D:\Python24\lib\subprocess.py", line 706, in _execute_child
TypeError: environment can only contain strings
It turns out that the strings in the "env" parameter have to b
12 matches
Mail list logo
