Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bpo-41810: Reintroduce types.EllipsisType, .NoneType & .NotImplementedType #22336

Merged
merged 13 commits into from Sep 22, 2020
Merged
Added EllipsisType to the documentation
  • Loading branch information
BvB93 committed Sep 21, 2020
commit 8aecfd52580453da2410f2c69d299a5d99016365
@@ -59,7 +59,8 @@ A small number of constants live in the built-in namespace. They are:
.. index:: single: ...; ellipsis literal
.. data:: Ellipsis

The same as the ellipsis literal "``...``". Special value used mostly in conjunction
The same as the ellipsis literal "``...``" and sole value of the type
Copy link
Member

@terryjreedy terryjreedy Sep 22, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The same as the ellipsis literal "``...``" and sole value of the type
The same as the ellipsis literal "``...``" and the only instance of

:data:`types.EllipsisType`. Special value used mostly in conjunction
with extended slicing syntax for user-defined container data types.


@@ -236,6 +236,13 @@ Standard names are defined for the following types:
Defaults to ``None``. Previously the attribute was optional.


.. data:: EllipsisType

The type of :data:`Ellipsis`.

.. versionadded:: 3.10


.. class:: TracebackType(tb_next, tb_frame, tb_lasti, tb_lineno)

The type of traceback objects such as found in ``sys.exc_info()[2]``.