On Thu, Jan 19, 2012 at 8:36 AM, Ethan Furman <et...@stoneleaf.us> wrote:
> Benjamin Peterson wrote: > >> 2012/1/19 Victor Stinner <victor.stin...@haypocalc.com>**: >> >>> http://bugs.python.org/**issue12773 <http://bugs.python.org/issue12773> :) >>>> >>> The bug is marked as close, whereas the bug exists in Python 3.2 and >>> has no been closed. The fix must be backported. >>> >> >> It's not a bug; it's a feature. >> > > 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. 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. Given that we haven't had any complaints about this in nearly a decade, the backport can't be important. Don't do it. -- --Guido van Rossum (python.org/~guido)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
