[issue9538] Replace confusing pseudoname 'object' in special methods section.

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.8, Python 3.9 -Python 3.3, Python 3.4 ___ Python tracker ___ ___ Python-

[issue9538] Replace confusing pseudoname 'object' in special methods section.

Terry J. Reedy added the comment: The problem, for me, is that in 3.3 Data Model, 'object' is being used with a 3rd meaning, 'generic class' (or possibly 'subclass of object', if indeed every 'class' must be 'object' subclass, in the strict sense of 'object'). This is in addition to 'object' t

[issue9538] Replace confusing pseudoname 'object' in special methods section.

peter recore added the comment: George, When I build the docs with my changes, the links from the method names seem to work the same way as they do in the existing docs. -- ___ Python tracker _

[issue9538] Replace confusing pseudoname 'object' in special methods section.

Georg Brandl added the comment: Note that Sphinx searches for "object.__foo__" when :meth:`__foo__` is used; this change will break all those links. For that reason I'm -1 to this change: I don't see the perceived issue as problematic anyway. -- __

[issue9538] Replace confusing pseudoname 'object' in special methods section.

peter recore added the comment: Here is a patch that implements Eric's suggestion. I am a new contributor and would welcome feedback on if this is correct or not. -- keywords: +patch nosy: +peterrecore Added file: http://bugs.python.org/file29815/issue9538.patch __

[issue9538] Replace confusing pseudoname 'object' in special methods section.

Éric Araujo added the comment: Good catch! Names listed under language reference section 3.3.1 actually all exist on object, e.g. object.__new__¹. It is section 3.3.2 that lists names that *can* be defined but don’t have a default implementation on object, so +1 on using “someclass” here to

[issue9538] Replace confusing pseudoname 'object' in special methods section.

Terry J. Reedy added the comment: I filed this because I just reread the __getattr(ibute)__ entries to respond to #8722 and found myself again stumbling over the 'object' confusion. -- ___ Python tracker _

[issue9538] Replace confusing pseudoname 'object' in special methods section.

Terry J. Reedy added the comment: I also think that in "In order to avoid infinite recursion in this method, its implementation should always call the base class method with the same name to access any attributes it needs, for example, object.__getattribute__(self, name).", 'the base class' s

[issue9538] Replace confusing pseudoname 'object' in special methods section.

New submission from Terry J. Reedy : In 3.3. Special method names, 'object' is used as a pseudo class name to prefix all the special method entries. This conflicts with the usual two Python meanings. 1. 'object' is the name of a specific class. So the entry for object.__getattribute__(self, n