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 Kenji Asuka (Asuka Kenji)
Recipients Kenji Asuka (Asuka Kenji), christian.heimes
Date 2017-10-11.08:23:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507710202.07.0.213398074469.issue31755@psf.upfronthosting.co.za>
In-reply-to
Content
You wrote:

> It only contains types that are not available as builtin.

I think the opposite is true.


As shown in the "Versions" field in the issue, this bug is Python 2 specific, so there is nothing to do with Python 3.

My point is not on 'dict', but on 'set'. So the history of 'dict' doesn't care.

As we can see there are names for:
- 'None' (types.NoneType)
- 'bool' (types.BooleanType)
- 'int' (types.IntType)
- 'long' (types.LongType)
- 'float' (types.FloatType)
- 'complex' (types.ComplexType)
- etc.

and more importantly:
- 'tuple' (types.TupleType)
- 'list' (types.ListType)
- 'dict' (types.DictType)

and since 'set' is also considered a built-in type (see https://docs.python.org/2/library/stdtypes.html), I can't see the reason WHY it is not considered a bug without having 'set' (types.SetType) in the module.
History
Date User Action Args
2017-10-11 08:23:22Kenji Asuka (Asuka Kenji)setrecipients: + Kenji Asuka (Asuka Kenji), christian.heimes
2017-10-11 08:23:22Kenji Asuka (Asuka Kenji)setmessageid: <1507710202.07.0.213398074469.issue31755@psf.upfronthosting.co.za>
2017-10-11 08:23:22Kenji Asuka (Asuka Kenji)linkissue31755 messages
2017-10-11 08:23:21Kenji Asuka (Asuka Kenji)create