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 abarnert, gvanrossum, levkivskyi, lukasz.langa, rhettinger
Date 2017-07-20.15:29:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1500564587.29.0.596988166095.issue25988@psf.upfronthosting.co.za>
In-reply-to
Content
IIRC, the original motivation for ABCs was to differentiate distinct uses of __getitem__ (we forever struggled with differentiating sequences from mapping).  It seems to me that this proposal is a step backwards.  Other than a feeling of lightness, I don't think this proposal does anything for us.  What is point of knowing an object is Subscriptable without knowing how it is to be used.

The OP has a sense that Mapping and Sequence are "too heavy" but I think the reality that useful classes almost never use __getitem__ in isolation; rather, it is part of a small constellation of methods that are typically used together.  I would prefer that collections.abc continue to reflect that reality.

Also, I worry that collections.abc is becoming cluttered.  The existence of use ABCs like MutableMapping is being drowned-out by one-trick-ponies.  We're developing an unfavorable ratio of theoretical building blocks versus the practical tools.
History
Date User Action Args
2017-07-20 15:29:47rhettingersetrecipients: + rhettinger, gvanrossum, lukasz.langa, abarnert, levkivskyi
2017-07-20 15:29:47rhettingersetmessageid: <1500564587.29.0.596988166095.issue25988@psf.upfronthosting.co.za>
2017-07-20 15:29:47rhettingerlinkissue25988 messages
2017-07-20 15:29:46rhettingercreate