Visitar URL original
Inconsistent import behavior when concurrent.futures.InterpreterPoolExecutor not exist · Issue #136380 · python/cpython · GitHub
Skip to content

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

Closed

Description

@aisk

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. added
    stdlibStandard Library Python modules in the Lib/ directory
    on Jul 7, 2025
  2. added a commit that references this issue on Jul 8, 2025
  3. added a commit that references this issue on Jul 8, 2025
  4. added
    3.14bugs and security fixes
    3.15bugs and security fixes
    on Jul 8, 2025
  5. added a commit that references this issue on Jul 8, 2025
  6. added a commit that references this issue on Jul 11, 2025
  7. added a commit that references this issue on Jul 12, 2025
  8. added a commit that references this issue on Jul 13, 2025
  9. added a commit that references this issue on Aug 4, 2025
  10. added a commit that references this issue on Aug 19, 2025
  11. added a commit that references this issue on Sep 9, 2025
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