[Python-Dev] Concurrent.futures: no type discovery for PyCharm (original) (raw)

Andrew Svetlov andrew.svetlov at gmail.com
Mon Apr 22 18:21:35 EDT 2019

I see the chicken and egg problem here. If we are talking about typing module usage -- typeshed is the type hints provider. If PyCharm doesn't want to use it -- it is not CPython problem.

I think there is no need to change python code itself but used tooling.

On Mon, Apr 22, 2019 at 11:06 PM Brett Cannon <brett at python.org> wrote:

On Sat, Apr 20, 2019 at 2:10 PM Inada Naoki <songofacandy at gmail.com> wrote: "import typing" is slow too. But is it so slow as to not do the right thing here and use the 'typing' module as expected? If you have so much work you need to launch some threads or processes to deal with it then a single import isn't going to be your biggest bottleneck. -Brett

2019年4月21日(日) 1:43 Ilya Kamenshchikov <ikamenshchikov at gmail.com>: alright, so would an import under TYPECHECKING guard be an option? like: from typing import TYPECHECKING if TYPECHECKING: from .process import ProcessPoolExecutor from .thread import ThreadPoolExecutor

Perhaps we can have both clarity and performance.

Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org

Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/andrew.svetlov%40gmail.com

-- Thanks, Andrew Svetlov

More information about the Python-Dev mailing list