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/2003-September/038039.html below:

[Python-Dev] SF #805304: bug or feature?

[Python-Dev] SF #805304: bug or feature? [Python-Dev] SF #805304: bug or feature?Martin v. Löwis martin at v.loewis.de
Sun Sep 14 18:12:42 EDT 2003
"Raymond Hettinger" <raymond.hettinger at verizon.net> writes:

> Once the fix is approved, there is a question of whether it should
> be backported.  The case against it is that some programs written 
> under Py2.3.1 or Py2.2.4 won't run on Py2.3.0 or Py2.2.3 and the 
> patch can be viewed as an API expansion.  The other point of view
> is that super objects should have always behaved this way and that
> the patch just fixes buggy behavior.

Whether it is a bug or not can be best clarified by looking at the
documentation: If it is documented that attributes of super objects
always follow MRO, then there is a bug. That might be a doc bug, but

Special cases aren't special enough to break the rules.

makes clear it wouldn't be a doc bug, but a bug in the code.

OTOH, if this is not documented at all, you clearly have a doc bug.

Regards,
Martin


More information about the Python-Dev mailing list

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