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 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? > > Does everyone agree this is the proper approach? I'm not familiar > with this code. Brett, if everyone agrees (ie, remains silent), > please fix this and add tests and a NEWS entry. Done. Even updated PEP 356 for you while I was at it. =) -Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060909/19a6f83f/attachment.html
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4