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/2007-March/072257.html below:

[Python-Dev] Breaking calls to object.__init__/__new__

[Python-Dev] Breaking calls to object.__init__/__new__ [Python-Dev] Breaking calls to object.__init__/__new__Guido van Rossum guido at python.org
Thu Mar 22 05:42:34 CET 2007
On 3/21/07, Terry Reedy <tjreedy at udel.edu> wrote:
> It seems to me that to get the exact behavior one wants at the apex of a
> diamond structure, one should subclass object and override .__init__  with
> a function that does not call object.__init__  and use that subclass as the
> apex instead of object itself.  Wouldn't this mask the behavior of
> object.__init__ and whatever changes decided on?

Yup, that's what I recommended for Aahz.

> (But having said that, I have no opiniou on what the default should be for
> those who don't do this.)

I do now -- for the single inheritance case, refusing extra args makes
the most sense too, so that sohuld be the default in 3.0. With a Py3k
warning in 2.6.

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)
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