[issue32596] Lazy import concurrent.futures.process and thread

Serhiy Storchaka added the comment: Thank you Inada-san. My first intention when I seen this code was to simplify it, but then I have found that it was an intentional change. It may be easy to detect such code and raise a syntax warning or error. Or get rid of this limitation and allow

[issue32596] Lazy import concurrent.futures.process and thread

Inada Naoki added the comment: See this comment. https://github.com/python/cpython/pull/5241#discussion_r162765765 -- ___ Python tracker ___

[issue32596] Lazy import concurrent.futures.process and thread

Serhiy Storchaka added the comment: What are issues with using global variable as import target? -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue32596] Lazy import concurrent.futures.process and thread

Change by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32596] Lazy import concurrent.futures.process and thread

Change by Cebtenzzre : -- nosy: +cebtenzzre ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32596] Lazy import concurrent.futures.process and thread

Antoine Pitrou added the comment: I don't think this was a good idea. Making some imports implicitly lazy introduces unpredictability in stdlib imports. Here is an example bug report: https://issues.apache.org/jira/browse/ARROW-11983 -- nosy: +pitrou

[issue32596] Lazy import concurrent.futures.process and thread

INADA Naoki added the comment: New changeset 4666ec597c38eea06a22bcfb4157d92a0abf891c by INADA Naoki in branch 'master': bpo-32596: Make lazy-load portable (GH-5316) https://github.com/python/cpython/commit/4666ec597c38eea06a22bcfb4157d92a0abf891c --

[issue32596] Lazy import concurrent.futures.process and thread

Change by INADA Naoki : -- pull_requests: +5162 ___ Python tracker ___ ___

[issue32596] Lazy import concurrent.futures.process and thread

Change by INADA Naoki : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue32596] Lazy import concurrent.futures.process and thread

INADA Naoki added the comment: New changeset 6690bb9f17d34eb3dec0aca8919d8d27d6c3c452 by INADA Naoki in branch 'master': bpo-32596: Lazy import concurrent.futures.process and thread (GH-5241)

[issue32596] Lazy import concurrent.futures.process and thread

Change by INADA Naoki : -- keywords: +patch pull_requests: +5087 stage: -> patch review ___ Python tracker ___

[issue32596] Lazy import concurrent.futures.process and thread

New submission from INADA Naoki : Since PEP 562 is implemented, we can use lazy imports easily. Asyncio uses concurrent.futures.Future and concurrent.futures.ThreadPoolExecutor, but not concurrent.futures.ProcessPoolExecutor by default. Since importing