This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients
Date 2007-04-03.02:33:47
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
At one time, I had explored adding some of these methods and then dropped the idea because it left super() with an odd mish-mash of methods that are 1) forwarded 2) not-supported 3) handled directly by the super-object itself.

For instance, the repr() of a super-object and is handled directly by the super object.  Likewise, the members are part of the super-object and not forwarded.  

The current state of affairs can be explained (approximately) with the notion that named methods are forwarded but not any of the syntax-assisted implicit calls.  This patch clutters that state-of-affairs for a questionable benefit.

If you want to push for this, it should be discussed on python-dev so we can reach a concensus on what super-objects should be expected to do and not do.  Is it clear that so.__self__ and repr(so) act on the super object while a call like so[x] will traverse the mro?

Also, if something like this does go in, please optimize the calls to PyString_FromString() to be invoked no more than once per Python session (otherwise, syntax driven implicit calls may end-up being slower than named method access).
History
Date User Action Args
2007-08-23 15:52:25adminlinkissue1498363 messages
2007-08-23 15:52:25admincreate