The message means just what it says. :-) There's no point in calling
object.__new__() with more than a class parameter, and any code that
did so was just dumping those args into a black hole.
The only time when it makes sense for object.__new__() to ignore extra
arguments is when it's not being ov
-On [20080213 21:02], Guido van Rossum ([EMAIL PROTECTED]) wrote:
>What __new__ deprecation warning?
Yes, sorry, I realized after sending that it might be a bit obtuse.
With 2.6:
DeprecationWarning: object.__new__() takes no parameters
return object.__new__(cls, uri)
--
Jeroen Ruigrok van de
What __new__ deprecation warning?
On Feb 13, 2008 11:50 AM, Jeroen Ruigrok van der Werven
<[EMAIL PROTECTED]> wrote:
> People,
>
> where can I find rationale/background on the __new__ deprecation warning in
> 2.6 (and I assume it's totally different in 3.0)?
>
> I could not find anything about it
People,
where can I find rationale/background on the __new__ deprecation warning in
2.6 (and I assume it's totally different in 3.0)?
I could not find anything about it in
http://docs.python.org/dev/3.0/whatsnew/3.0.html or
http://docs.python.org/dev/whatsnew/2.6.html
Cheers,
--
Jeroen Ruigrok
