Skip to content

Inconsistent import behavior when concurrent.futures.InterpreterPoolExecutor not exist #136380

Closed
Closed
Inconsistent import behavior when concurrent.futures.InterpreterPoolExecutor not exist#136380
Labels
3.14bugs and security fixes3.15bugs and security fixesstdlibStandard Library Python modules in the Lib/ directorytopic-subinterpreterstype-bugAn unexpected behavior, bug, or error

Description

@aisk
aisk
opened on Jul 7, 2025

Bug report

Bug description:

When the _interpreters module which under the hood to implement InterpreterPoolExecutor does not exist, import concurrent.futures.InterpreterPoolExecutor will result None, instead of ImportError.

A PR is on the way to address this.

CPython versions tested on:

CPython main branch

Operating systems tested on:

No response

Linked PRs

Activity

  1. aisk
    added
    type-bugAn unexpected behavior, bug, or error
    topic-subinterpreters
    on Jul 7, 2025
  2. github-project-automation
    added this to Subinterpreterson Jul 7, 2025
  3. github-project-automation
    moved this to Todo in Subinterpreterson Jul 7, 2025
  4. picnixz
    added
    stdlibStandard Library Python modules in the Lib/ directory
    on Jul 7, 2025
  5. sobolevn
    added a commit that references this issue on Jul 8, 2025

    gh-136380: Fix import behavior for `concurrent.futures.InterpreterPoo…

    490eea0
  6. miss-islington
    added a commit that references this issue on Jul 8, 2025

    pythongh-136380: Fix import behavior for `concurrent.futures.Interpre…

    24799ac
  7. picnixz
    added
    3.14bugs and security fixes
    3.15bugs and security fixes
    on Jul 8, 2025
  8. sobolevn
    added a commit that references this issue on Jul 8, 2025

    [3.14] gh-136380: Fix import behavior for `concurrent.futures.Interpr…

    f937b9f
  9. sobolevn
    closed this as completedon Jul 8, 2025
  10. github-project-automation
    moved this from Todo to Done in Subinterpreterson Jul 8, 2025
  11. AndPuQing
    added a commit that references this issue on Jul 11, 2025

    pythongh-136380: Fix import behavior for `concurrent.futures.Interpre…

    272d235
  12. Pranjal095
    added a commit that references this issue on Jul 12, 2025

    pythongh-136380: Fix import behavior for `concurrent.futures.Interpre…

    9744a5f
  13. picnixz
    added a commit that references this issue on Jul 13, 2025

    pythongh-136380: Fix import behavior for `concurrent.futures.Interpre…

    f0eaa06
  14. taegyunkim
    added a commit that references this issue on Aug 4, 2025

    pythongh-136380: Fix import behavior for `concurrent.futures.Interpre…

    df97794
  15. Agent-Hellboy
    added a commit that references this issue on Aug 19, 2025

    pythongh-136380: Fix import behavior for `concurrent.futures.Interpre…

    cbaf664
  16. kumaraditya303
    added a commit that references this issue on Sep 9, 2025

    [3.14] pythongh-136380: Fix import behavior for `concurrent.futures.I…

    ccc3386
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    3.14bugs and security fixes3.15bugs and security fixesstdlibStandard Library Python modules in the Lib/ directorytopic-subinterpreterstype-bugAn unexpected behavior, bug, or error

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions