[Python-Dev] Concurrent.futures: no type discovery for PyCharm
Inada Naoki
songofacandy at gmail.com
Sat Apr 20 17:08:36 EDT 2019
More information about the Python-Dev mailing list
Sat Apr 20 17:08:36 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 ]
"import typing" is slow too. 2019年4月21日(日) 1:43 Ilya Kamenshchikov <ikamenshchikov at gmail.com>: > alright, so would an import under TYPE_CHECKING guard be an option? like: > > from typing import TYPE_CHECKING > if TYPE_CHECKING: > from .process import ProcessPoolExecutor > from .thread import ThreadPoolExecutor > > > Perhaps we can have both clarity and performance. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20190421/613e466c/attachment.html>
- 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 ]
More information about the Python-Dev mailing list