<div class="gmail_quote">On Thu, Jan 19, 2012 at 8:36 AM, Ethan Furman <span dir="ltr"><<a href="mailto:ethan@stoneleaf.us">ethan@stoneleaf.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">Benjamin Peterson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2012/1/19 Victor Stinner <<a href="mailto:victor.stinner@haypocalc.com" target="_blank">victor.stinner@haypocalc.com</a>><u></u>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<a href="http://bugs.python.org/issue12773" target="_blank">http://bugs.python.org/<u></u>issue12773</a> :)<br>
</blockquote>
The bug is marked as close, whereas the bug exists in Python 3.2 and<br>
has no been closed. The fix must be backported.<br>
</blockquote>
<br>
It's not a bug; it's a feature.<br>
</blockquote>
<br></div>
Where does one draw the line between feature and bug? As a user I'm inclined to classify this as a bug: __doc__ was writable with old-style classes; __doc__ is writable with new-style classes with any metaclass; and there exists no good reason (that I'm aware of ;) for __doc__ to not be writable.</blockquote>
<div><br></div><div>Like it or not, this has worked this way ever since new-style classes were introduced. That has made it a de-facto feature. We should not encourage people to write code that works with a certain bugfix release but not with the previous bugfix release of the same feature release.</div>
<div><br></div><div>Given that we haven't had any complaints about this in nearly a decade, the backport can't be important. Don't do it.</div></div><div><br></div>-- <br>--Guido van Rossum (<a href="http://python.org/~guido">python.org/~guido</a>)<br>