On 9/7/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
Should be. There was no proper __unicode__() originally so that's why this whole problem came up in the first place.
I am not terribly anymore either since Georg and Richard rewrote the whole thing. =)
OK.
-Brett
On 9/5/06, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
> > [MAL]
> > The proper fix would be to introduce a tp_unicode slot and let
> > this decide what to do, ie. call .__unicode__() methods on instances
> > and use the .__name__ on classes.
>
> That was my bug reaction and what I said on the bug report. Kind of
> surprised one doesn't already exist.
>
> > I think this would be the right way to go for Python 2.6. For
> > Python 2.5, just dropping this .__unicode__ method on exceptions
> > is probably the right thing to do.
>
> Neal, do you want to rip it out or should I?
Is removing __unicode__ backwards compatible with 2.4 for both
instances and exception classes?
Should be. There was no proper __unicode__() originally so that's why this whole problem came up in the first place.
Does everyone agree this is the proper approach? I'm not familiar
with this code.
I am not terribly anymore either since Georg and Richard rewrote the whole thing. =)
Brett, if everyone agrees (ie, remains silent),
please fix this and add tests and a NEWS entry.
OK.
-Brett
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
