John Nagle <[EMAIL PROTECTED]> wrote:
...
> > Are you looking at p. 109 of the 2nd edition of the Nutshell?
>
> No, I'm looking at the original edition from 2003. That
> was what Borders had in stock late last year.
Eeek -- the 2nd edition came out in July 2006, and several months later
Alex Martelli wrote:
> John Nagle <[EMAIL PROTECTED]> wrote:
>...
>
>>The real problem is the published books on Python:
>>
>>"Learning Python", by Lutz and Ascher:
>>"str(string) -- returns the string representation of any object."
>>
>>"Python in a Nutshell", by Martelli
>>Doesn'
John Nagle <[EMAIL PROTECTED]> wrote:
...
> The real problem is the published books on Python:
>
> "Learning Python", by Lutz and Ascher:
> "str(string) -- returns the string representation of any object."
>
> "Python in a Nutshell", by Martelli
> Doesn't really address the issue,
On Mon, 19 Mar 2007 17:01:23 +, John Nagle wrote:
>> Hi John, I'm not at all an expert around here but my understanding of
>> the workflow is that bug reports should be submitted to the tracker at
>> sourceforge. There is no guarantee that they will be noticed there but
>> the chances there ar
John Nagle wrote:
> and when we get to
> Unicode-only strings, "str" will never raise a conversion exception.
On *strings*, maybe, but objects can implement __str__ in
arbitrary ways, so you can't say anything in general about
what str() will do.
--
Greg
--
http://mail.python.org/mailman/listinf
Daniel Nogradi wrote:
>> The Python documentation for "str" says
>> "str([object]) :
>> Return a string containing a nicely printable representation of an
>> object."
>>
>> However, there's no mention of the fact that "str" of a Unicode string
>> with non-ASCII characters will raise a conversi
