Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLN remove backward compat and rely on multiprocessing for win reduction #394

Merged
merged 9 commits into from
Apr 14, 2023

Conversation

tomMoral
Copy link
Collaborator

No description provided.

@ogrisel
Copy link
Collaborator

ogrisel commented Apr 13, 2023

The windows py38 deadlock does not appear on master. So maybe this backward compat is required at least for Python 3.8?

The py311 failures are already present on master and are therefore unrelated to this PR.

@tomMoral
Copy link
Collaborator Author

The windows py38 deadlock does not appear on master. So maybe this backward compat is required at least for Python 3.8?

The py38 failure on the first commit is on macos so I don't think it is related to this PR in fact, I think we both misread this 😅

@tomMoral tomMoral merged commit 410b2c2 into joblib:master Apr 14, 2023
@tomMoral tomMoral deleted the CLN_remove_backcompat branch April 14, 2023 10:27
@ogrisel
Copy link
Collaborator

ogrisel commented Apr 14, 2023

@tomMoral we need to document the change in the changelog. In particular, I think this is a bugfix for nested use of loky under Python 3.11 (compared to the last released version).

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