Message 380998 - Python tracker

➜

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	andyharrington, docs@python, rhettinger
Date	2020-11-15.01:28:27
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1605403707.86.0.559549389336.issue42359@roundup.psfhosted.org>
In-reply-to

Content
I think the current wording is fine. After the type/class unification we tend to use the words "type" and "class" almost interchangeably. For builtins, we still tend to say type though. The language itself tends to mix the terms as well: >>> class A: pass >>> type(A) <class 'type'> >>> type(list) <class 'type'>

I think the current wording is fine.  After the type/class unification we tend to use the words "type" and "class" almost interchangeably.  For builtins, we still tend to say type though.

The language itself tends to mix the terms as well:

>>> class A:
       pass

>>> type(A)
<class 'type'>
>>> type(list)
<class 'type'>

History
Date	User	Action	Args
2020-11-15 01:28:27	rhettinger	set	recipients: + rhettinger, andyharrington, docs@python
2020-11-15 01:28:27	rhettinger	set	messageid: <1605403707.86.0.559549389336.issue42359@roundup.psfhosted.org>
2020-11-15 01:28:27	rhettinger	link	issue42359 messages
2020-11-15 01:28:27	rhettinger	create