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 BvB93
Recipients BvB93
Date 2020-09-18.19:29:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1600457340.51.0.170346163147.issue41810@roundup.psfhosted.org>
In-reply-to
Content
`Ellipsis` is one of the few builtin objects whose type is not exposed via the `types` module. 
This is not really an issue during runtime, as you can always call `type(Ellipsis)`, but for the purpose of typing it is detrimental; the lack of suitable type means that it is impossible to properly annotate a function which takes or returns `Ellipsis` (unless one is willing to resort to the use of non-public types: https://github.com/python/typeshed/issues/3556).

In order to resolve this issue I propose to reintroduce `types.EllipsisType`. This should be a fairly simple process, so if there are no objections I'd be willing to give it a shot.
History
Date User Action Args
2020-09-18 19:29:00BvB93setrecipients: + BvB93
2020-09-18 19:29:00BvB93setmessageid: <1600457340.51.0.170346163147.issue41810@roundup.psfhosted.org>
2020-09-18 19:29:00BvB93linkissue41810 messages
2020-09-18 19:29:00BvB93create