[Python-Dev] __str__ vs. __unicode__
bac at OCF.Berkeley.EDU
Thu Feb 24 21:10:15 CET 2005
Walter Dörwald wrote:
> Brett C. wrote:
>> Walter Dörwald wrote:
>>> M.-A. Lemburg wrote:
>>>> I don't have a clear picture of what the consensus currently
>>>> looks like :-)
>>>> If we're going for for a solution that implements the hook
>>>> awareness for all __<typename>__ hooks, I'd be +1 on that.
>>>> If we only touch the __unicode__ case, we'd only be created
>>>> yet another special case. I'd vote -0 on that.
>>> Here's the patch that implements this for int/long/float/unicode:
>> Any movement on this? +1 for making things work like str; if a
>> subclass overrides __str__ it should use that method. If correctness
>> of what is
>> returned is a worry then a check could be tossed in before the value
>> is returned.
> It already works that way:
> Python 2.5a0 (#1, Feb 24 2005, 16:25:04)
> [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-113)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> class u(unicode):
> ... def __unicode__(self): return 42
Well then I am +1 on doing this.
Since this is a semantic change probably need Guido to OK this?
More information about the Python-Dev