PEP 613 (Explicit Type Aliases) tracker

This issue is supposed to track when we can start to use explicit type aliases (PEP 613) in typeshed. Support is needed in released versions of:

mypy (Support PEP 613 mypy#9404)
- Explicit type aliases fail in typeshed mypy#12422
pytype (Support PEP 613: Explicit Type Aliases google/pytype#787)
- Problems with explicit type aliases in typeshed google/pytype#1159
pyright (Implement PEP 613 microsoft/pyright#655)
pyre
PyCharm PY-42334

@rchen152

@rchen152 I am sorry for the mention spam, but does pytype support PEP 613? If not, would you mind me creating a ticket that we can reference from here?

Supported since PyCharm 2020.3 https://youtrack.jetbrains.com/issue/PY-42334

pytype doesn't support this yet. Opened google/pytype#787.

I used this simple script to test this feature.

from typing_extensions import TypeAlias

Alias1 = str
Alias2: TypeAlias = str

def foo() -> Alias1: pass
def bar() -> Alias2: pass

reveal_type(foo)
reveal_type(bar)

mypy 0.930 now supports this.

pytype-2022.03.21 supports explicit type aliases.

Seems like there's nothing left to do here :)

Reopening as mypy still seems to have problems. #7534

@rchen152

@rchen152, #7534 also has several pytype errors, but they all look like valid type aliases to me — any idea what the problem is? :)

Whoops, that's embarrassing XD
It looks almost like the type aliases aren't being stored at all - I'll investigate.

mypy and pytype are now fixed. 🎉

Does the closing of this issue mean that TypeAlias can now be used in TypeShed?

if yes, this should probably be edited:

typeshed/CONTRIBUTING.md

Lines 241 to 242 in be64b01

    
           - [PEP 613](https://www.python.org/dev/peps/pep-0613/) (TypeAlias): 
        
             see [#4913](https://github.com/python/typeshed/issues/4913)

Does the closing of this issue mean that TypeAlias can now be used in TypeShed?

if yes, this should probably be edited:

typeshed/CONTRIBUTING.md

Lines 241 to 242 in be64b01

- [PEP 613](https://www.python.org/dev/peps/pep-0613/) (TypeAlias):

see [#4913](https://github.com/python/typeshed/issues/4913)

It does — and yes, CONTRIBUTING does need to be edited :) I think the guidance on ParamSpec is also slightly out of date.

PR welcome, if you'd like to help out!

Does the closing of this issue mean that TypeAlias can now be used in TypeShed?
if yes, this should probably be edited:

typeshed/CONTRIBUTING.md

Lines 241 to 242 in be64b01

- [PEP 613](https://www.python.org/dev/peps/pep-0613/) (TypeAlias):

see [#4913](https://github.com/python/typeshed/issues/4913)

It does — and yes, CONTRIBUTING does need to be edited :) I think the guidance on ParamSpec is also slightly out of date.

PR welcome, if you'd like to help out!

#8397 created to address this

Navigation Menu

Repository navigation

PEP 613 (Explicit Type Aliases) tracker #4913

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

	- [PEP 613](https://www.python.org/dev/peps/pep-0613/) (TypeAlias):
	see [#4913](https://github.com/python/typeshed/issues/4913)

PEP 613 (Explicit Type Aliases) tracker #4913

Description

Activity

srittau commented on Jan 6, 2021

sproshev commented on Jan 6, 2021

rchen152 commented on Jan 7, 2021

srittau commented on Jun 14, 2021

srittau commented on Dec 22, 2021

rchen152 commented on Mar 22, 2022

AlexWaygood commented on Mar 22, 2022

srittau commented on Mar 22, 2022

AlexWaygood commented on Mar 22, 2022

rchen152 commented on Mar 22, 2022

srittau commented on Mar 30, 2022

laundmo commented on Apr 4, 2022

AlexWaygood commented on Apr 4, 2022

kkirsche commented on Jul 25, 2022

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions