[Python-Dev] 2.5 status (original) (raw)
Brett Cannon brett at python.org
Thu Sep 7 19:39:20 CEST 2006
- Previous message: [Python-Dev] 2.5 status
- Next message: [Python-Dev] 2.5 status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 9/7/06, Neal Norwitz <nnorwitz at gmail.com> wrote:
On 9/5/06, Brett Cannon <brett at python.org> wrote: > > > [MAL] > > The proper fix would be to introduce a tpunicode 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060907/3def1449/attachment.htm
- Previous message: [Python-Dev] 2.5 status
- Next message: [Python-Dev] 2.5 status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]