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 yselivanov
Recipients brett.cannon, ezio.melotti, rhettinger, stutzbach, yselivanov
Date 2015-11-18.22:46:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1447886761.83.0.490308164035.issue25637@psf.upfronthosting.co.za>
In-reply-to
Content
> I guess is the objection of putting concrete ABCs in the abc module is that the abc module contains the actual code to implement ABCs and not ABCs themselves.

I think it's a rather weak objection.  Having some basic (and fundamental!) ABCs defined along with ABCMeta won't hurt.

> Personally I would be fine with a submodule within abc like abc.interfaces.

> Personally I'm starting to warm to the idea of sticking ABCs in proper packages as e.g. functools.abc for Callable; namespaces are one honking great idea after all. :)

It will be hard to find proper namespace for things like Hashable and Awaitable.  That's why I like the idea of putting them in the top-level 'abc' module.
History
Date User Action Args
2015-11-18 22:46:01yselivanovsetrecipients: + yselivanov, brett.cannon, rhettinger, stutzbach, ezio.melotti
2015-11-18 22:46:01yselivanovsetmessageid: <1447886761.83.0.490308164035.issue25637@psf.upfronthosting.co.za>
2015-11-18 22:46:01yselivanovlinkissue25637 messages
2015-11-18 22:46:01yselivanovcreate