Message113194
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, name) says to avoid circularity by calling
object.__getattribute__(self, name), which looks circular and requires a bit a mental work by the reader to properly understand. Ditto for
object.__setattr__(self, name, value) calling
object.__setattr__(self, name, value)
2. Non-specifically, 'object' is usually understood to mean any Python object, not just a class. But the signatures as written require that 'object' specifically be a class and 'object' does not convey that.
So for both reasons, I propose that the pseudoname 'object' be replaces with 'class' or 'someclass' |
|
Date |
User |
Action |
Args |
2010-08-07 20:04:39 | terry.reedy | set | recipients:
+ terry.reedy, georg.brandl, docs@python |
2010-08-07 20:04:39 | terry.reedy | set | messageid: <1281211479.21.0.733519342396.issue9538@psf.upfronthosting.co.za> |
2010-08-07 20:04:37 | terry.reedy | link | issue9538 messages |
2010-08-07 20:04:37 | terry.reedy | create | |
|