John Nagle wrote:
On 8/20/2010 8:41 AM, Aahz wrote:
In article<4c5eef7f$0$1609$742ec...@news.sonic.net>,
John Nagle wrote:
This looks like code that will do the wrong thing in
Python 2.6 for characters in the range 128-255. Those are
illegal in type "str", but this code is constructing
On 8/20/10 1:50 PM, John Nagle wrote:
On 8/20/2010 8:41 AM, Aahz wrote:
In article<4c5eef7f$0$1609$742ec...@news.sonic.net>,
John Nagle wrote:
This looks like code that will do the wrong thing in
Python 2.6 for characters in the range 128-255. Those are
illegal in type "str", but this code is
On 8/20/2010 8:41 AM, Aahz wrote:
In article<4c5eef7f$0$1609$742ec...@news.sonic.net>,
John Nagle wrote:
This looks like code that will do the wrong thing in
Python 2.6 for characters in the range 128-255. Those are
illegal in type "str", but this code is constructing such
values with "c
In article <4c5eef7f$0$1609$742ec...@news.sonic.net>,
John Nagle wrote:
>
> This looks like code that will do the wrong thing in
>Python 2.6 for characters in the range 128-255. Those are
>illegal in type "str", but this code is constructing such
>values with "chr".
WDYM "illegal"?
--
Aahz
