A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/attachments/20060909/19a6f83f/attachment.html below:

<br><br><div><span class="gmail_quote">On 9/7/06, <b class="gmail_sendername">Neal Norwitz</b> &lt;<a href="mailto:nnorwitz@gmail.com">nnorwitz@gmail.com</a>&gt; 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 &lt;<a href="mailto:brett@python.org">brett@python.org</a>&gt; wrote:<br>&gt;<br>&gt; &gt; [MAL]<br>&gt; &gt; The proper fix would be to introduce a tp_unicode slot and let<br>&gt; &gt; this decide what to do, ie. call .__unicode__() methods on instances
<br>&gt; &gt; and use the .__name__ on classes.<br>&gt;<br>&gt; That was my bug reaction&nbsp;&nbsp;and what I said on the bug report.&nbsp;&nbsp;Kind of<br>&gt; surprised one doesn't already exist.<br>&gt;<br>&gt; &gt; I think this would be the right way to go for Python 
2.6. For<br>&gt; &gt; Python 2.5, just dropping this .__unicode__ method on exceptions<br>&gt; &gt; is probably the right thing to do.<br>&gt;<br>&gt; 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?<br><br>Does everyone agree this is the proper approach?&nbsp;&nbsp;I'm not familiar<br>with this code.&nbsp;&nbsp;Brett, if everyone agrees (ie, remains silent),<br>please fix this and add tests and a NEWS entry.
</blockquote><div><br>Done.&nbsp; Even updated PEP 356 for you while I was at it.&nbsp; =)<br><br>-Brett <br></div><br></div><br>

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