From b2a2dcda3a1511d7fdbf6c290f33cb68a478e5a0 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Sun, 11 Jan 2026 08:49:37 +0100 Subject: [PATCH] [3.13] Remove outdated comment about `excess_args` warning in `object.__init__` (GH-143669) (#143681) Remove outdated comment about `excess_args` warning in `object.__init__` (GH-143669) The code emitting a warning was removed in 96384b93aae1d1e45dda21c4024d7d083c91626d. (cherry picked from commit 03e6457096d452859fb4cfd418dc9268c6454c29) Co-authored-by: Manuel Jacob --- Objects/typeobject.c | 6 ------ 1 file changed, 6 deletions(-) diff --git a/Objects/typeobject.c b/Objects/typeobject.c index 01f84ab50858..ded0f22b4e10 100644 --- a/Objects/typeobject.c +++ b/Objects/typeobject.c @@ -6101,12 +6101,6 @@ PyTypeObject PyType_Type = { symmetrically, __new__() complains about excess arguments unless __init__() is overridden and __new__() is not overridden (IOW, if __new__() is overridden or __init__() is not overridden). - - However, for backwards compatibility, this breaks too much code. - Therefore, in 2.6, we'll *warn* about excess arguments when both - methods are overridden; for all other cases we'll use the above - rules. - */ /* Forward */ -- 2.47.3