Skip to content

Use a dedicated multiprocessing context (of type "fork")#655

Merged
sirosen merged 4 commits into
mainfrom
use-an-mp-context
Mar 2, 2026
Merged

Use a dedicated multiprocessing context (of type "fork")#655
sirosen merged 4 commits into
mainfrom
use-an-mp-context

Conversation

@sirosen

@sirosen sirosen commented Mar 1, 2026

Copy link
Copy Markdown
Collaborator

In order to ensure that nose2 isn't harmed by or harmful to users who set the
multiprocessing process start method (globally), it now uses a multiprocessing
context for the "mp" (multiprocess) plugin.

This also ensures that nose2 continues to use "fork" on Python 3.14+.

airtower-luna and others added 2 commits March 1, 2026 17:30
Tests with coverage often produce "No data to report" errors with
"forkserver", which became the default on POSIX systems with Python
3.14. Using a multiprocessing context allows changing the start method
only for the mp plugin.
@sirosen

sirosen commented Mar 1, 2026

Copy link
Copy Markdown
Collaborator Author

Ah, hello Windows CI. Let's see if we can come to some kind of agreement about multiprocessing. 😄

sirosen added 2 commits March 1, 2026 17:57
The two context types have different _types_, which results in mypy
failures. Cool. Fixy fix.
@sirosen sirosen merged commit d90af48 into main Mar 2, 2026
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants