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 levkivskyi
Recipients Cameron Trando, gvanrossum, levkivskyi
Date 2019-08-22.19:37:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1566502669.43.0.233498637375.issue37920@roundup.psfhosted.org>
In-reply-to
Content
There is an (old) similar proposal https://github.com/python/typing/issues/402 btw.

Taking into account that this can be made only in 3.9, what is the benefit over ``from __future__ import annotations`` (that one can use already) do you see?

IMO there are only rare cases of type aliases and base classes, so I don't see much benefit. Also making it generic will require importing ``typing`` from ``os`` which may make it slower to import (``typing`` is a really heavy module, in particular because it imports many other modules).
History
Date User Action Args
2019-08-22 19:37:49levkivskyisetrecipients: + levkivskyi, gvanrossum, Cameron Trando
2019-08-22 19:37:49levkivskyisetmessageid: <1566502669.43.0.233498637375.issue37920@roundup.psfhosted.org>
2019-08-22 19:37:49levkivskyilinkissue37920 messages
2019-08-22 19:37:49levkivskyicreate