Author yselivanov
Recipients brett.cannon, ezio.melotti, martin.panter, ncoghlan, rhettinger, stutzbach, terry.reedy, yselivanov
Date 2016-01-02.23:03:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1451775837.5.0.11831900307.issue25637@psf.upfronthosting.co.za>
In-reply-to
Content
> Did anyone consider moving these near the “types” module, either directly inside, or as a “types.abc” submodule? In my mind, these ABCs would fit reasonably well there. They are related to built-in types, but do not have built-in names.

Big -1.  Let's avoid nesting 'abc' modules throughout the standard library.  One of the good practices in Python is to import modules, not classes from modules.  With 'types.abc' I'll have to import 'from types import abc', and then, in the code, I won't be so sure which 'abc' is it -- 'abc', 'types.abc', 'collections.abc' etc.

Putting ABCs in the 'types' module directly also doesn't feel right and can confuse users.  'types' already contains things like 'GeneratorType', 'CoroutineType' etc, which are actual types (not ABCs).
History
Date User Action Args
2016-01-02 23:03:57yselivanovsetrecipients: + yselivanov, brett.cannon, rhettinger, terry.reedy, ncoghlan, stutzbach, ezio.melotti, martin.panter
2016-01-02 23:03:57yselivanovsetmessageid: <1451775837.5.0.11831900307.issue25637@psf.upfronthosting.co.za>
2016-01-02 23:03:57yselivanovlinkissue25637 messages
2016-01-02 23:03:57yselivanovcreate