[Python-Dev] Concurrent.futures: no type discovery for PyCharm (original) (raw)
Nathaniel Smith njs at pobox.com
Sat Apr 20 20:13:27 EDT 2019
- Previous message (by thread): [Python-Dev] Concurrent.futures: no type discovery for PyCharm
- Next message (by thread): [Python-Dev] Concurrent.futures: no type discovery for PyCharm
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Apr 20, 2019 at 2:11 PM Inada Naoki <songofacandy at gmail.com> wrote:
"import typing" is slow too.
Many static analysis tools will also accept:
TYPE_CHECKING = False if TYPE_CHECKING: ...
At least mypy and pylint both treat all variables named TYPE_CHECKING as true, regardless of where they came from. I'm not sure if this is intentional or because they're cutting corners, but it works...
-n
-- Nathaniel J. Smith -- https://vorpus.org
- Previous message (by thread): [Python-Dev] Concurrent.futures: no type discovery for PyCharm
- Next message (by thread): [Python-Dev] Concurrent.futures: no type discovery for PyCharm
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]