[issue26391] typing: Specialized sub-classes of Generic never call __init__

Changes by Guido van Rossum : -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue26391] typing: Specialized sub-classes of Generic never call __init__

Roundup Robot added the comment: New changeset be3c4151d9bf by Guido van Rossum in branch '3.5': Many changes from the upstream repo (https://github.com/python/typing). https://hg.python.org/cpython/rev/be3c4151d9bf -- nosy: +python-dev ___ Python

[issue26391] typing: Specialized sub-classes of Generic never call __init__

Guido van Rossum added the comment: This is fixed upstream (https://github.com/python/typing/commit/8c6aaf30751fec28f1a7e467139ae23c9cc30c81). I'm keeping this open until I've merged typing.py into CPython 3.5 and 3.6. -- ___ Python tracker

[issue26391] typing: Specialized sub-classes of Generic never call __init__

Guido van Rossum added the comment: Actually, I just realized why this is. Generic.__new__() calls next_in_mro.__new__(_gorg(cls)). Here next_in_mro is just object, but _gorg(cls) is Foo, in the case where cls is Bar (i.e. Foo[str]). The _gorg() call strips the [str] part of the type. So far

[issue26391] typing: Specialized sub-classes of Generic never call __init__

Changes by STINNER Victor : -- title: Specialized sub-classes of Generic never call __init__ -> typing: Specialized sub-classes of Generic never call __init__ ___ Python tracker