Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

recent -X options do not auto-propagate to multiprocessing processes #146004

Copy link
Copy link
@gpshead

Description

@gpshead
Issue body actions

Bug report

Bug description:

-X lazy_imports, -X thread_inherit_context, and -X context_aware_warnings are not inherited via subprocess._args_from_interpreter_flags() so multiprocessing spawned child processes do not inherit these -X settings unless the user happens to be using the dangerous non-default "fork" start method.

We should consider this for every -X option added. In general the answer should be "yes". There's a list in Lib/subprocess.py to update. (could we automate this by making the list an opt-out instead of a remember-when-adding-a-feature-to-opt-in list?)

Linked PRs

Reactions are currently unavailable

Metadata

Metadata

Labels

3.13bugs and security fixesbugs and security fixes3.14bugs and security fixesbugs and security fixes3.15pre-release feature fixes, bugs and security fixespre-release feature fixes, bugs and security fixesstdlibStandard Library Python modules in the Lib/ directoryStandard Library Python modules in the Lib/ directorytopic-multiprocessingtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.