<br><br><div><span class="gmail_quote">On 9/7/06, <b class="gmail_sendername">Neal Norwitz</b> <<a href="mailto:nnorwitz@gmail.com">nnorwitz@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 9/5/06, Brett Cannon <<a href="mailto:brett@python.org">brett@python.org</a>> wrote:<br>><br>> > [MAL]<br>> > The proper fix would be to introduce a tp_unicode slot and let<br>> > this decide what to do, ie. call .__unicode__() methods on instances
<br>> > and use the .__name__ on classes.<br>><br>> That was my bug reaction and what I said on the bug report. Kind of<br>> surprised one doesn't already exist.<br>><br>> > I think this would be the right way to go for Python
2.6. For<br>> > Python 2.5, just dropping this .__unicode__ method on exceptions<br>> > is probably the right thing to do.<br>><br>> Neal, do you want to rip it out or should I?<br><br>Is removing __unicode__ backwards compatible with
2.4 for both<br>instances and exception classes?</blockquote><div><br> Should be. There was no proper __unicode__() originally so that's why this whole problem came up in the first place.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Does everyone agree this is the proper approach? I'm not familiar<br>with this code.</blockquote><div><br>I am not terribly anymore either since Georg and Richard rewrote the whole thing. =) <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Brett, if everyone agrees (ie, remains silent),<br>please fix this and add tests and a NEWS entry.</blockquote><div><br>OK.<br></div><br>-Brett<br></div><br>