New submission from Mathias Rav:
The documentation of typing.TYPE_CHECKING has an example (introduced in issue
#26141) that would lead to NameError at runtime. The example shows how to limit
the import of "expensive_mod" to type checkers, but then goes on to use
"expensive_mod.some_type" in a type annotation that is evaluated at runtime
("local_var: expensive_mod.some_type"). The use case of TYPE_CHECKING is
probably meant for type annotations placed in comments, e.g. "local_var #
type: expensive_mod.some_type".
----------
assignee: docs@python
components: Documentation
messages: 291085
nosy: docs@python, rav
priority: normal
severity: normal
status: open
title: typing.TYPE_CHECKING doc example is incorrect
type: enhancement
versions: Python 3.4, Python 3.5, Python 3.6, Python 3.7
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
