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.

Sign up for GitHub

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

Jump to bottom

BaseSolver.solve() multiprocessing is broken on system's defaulting to spawn context for windows #3987

Open
kratman opened this issue Apr 10, 2024 · 4 comments
Open

BaseSolver.solve() multiprocessing is broken on system's defaulting to spawn context for windows #3987

kratman opened this issue Apr 10, 2024 · 4 comments
Assignees
@BradyPlanden
Labels
priority: high To be resolved as soon as possible

Comments

@kratman
Copy link
Contributor

kratman commented Apr 10, 2024

Follow up to #3975

It's worth noting that this only fixes #3974 for darwin systems and protects linux systems from the default context change in Python 3.14. Windows systems will still require the main guard discussed in #3974.
@agriyakhetarpal agriyakhetarpal added the priority: high To be resolved as soon as possible label Apr 12, 2024
@agriyakhetarpal
Copy link
Member

Labelled the issue with high priority so that we remember to get this done before v24.5rc0

@agriyakhetarpal agriyakhetarpal added the release blocker Issues that need to be addressed before the creation of a release label Apr 25, 2024
@kratman
Copy link
Contributor Author

kratman commented May 3, 2024

@BradyPlanden Any update on this ticket?

@martinjrobins martinjrobins mentioned this issue May 14, 2024
Open
@brosaplanella
Copy link
Member

Following up on the dev meeting, we agreed to include a more informative error for Windows, and fixes can be done as part of #4087

@agriyakhetarpal agriyakhetarpal removed the release blocker Issues that need to be addressed before the creation of a release label May 17, 2024
@agriyakhetarpal
Copy link
Member

Removed this from blocking the release based on comments from the dev meeting and on the issue linked above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BradyPlanden BradyPlanden

Labels
priority: high To be resolved as soon as possible
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kratman @brosaplanella @BradyPlanden @agriyakhetarpal