Skip to content

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

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

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.15pre-release feature fixes, bugs 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