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

[reopen2] Release GIL when doing standalone solves #363

Merged
merged 7 commits into from
Jan 13, 2025

Conversation

fabinsch
Copy link
Collaborator

same PR as #359. I am sorry I did a bad command while trying to run the CI on the original PR by @jberg5.

@fabinsch fabinsch force-pushed the topic/gil branch 3 times, most recently from 9ebcc46 to b073bf7 Compare January 10, 2025 15:33
@fabinsch
Copy link
Collaborator Author

From my side it's good to merge, all the ci are passing (except the one for ros which is not affected here)

@jberg5
Copy link
Contributor

jberg5 commented Jan 10, 2025

Thanks @fabinsch! Once this is merged, what’s the rough timeline for the changes on devel to be released?

@fabinsch
Copy link
Collaborator Author

After the merge here and of PR 361 (for Python 3.13 release on pypi) we should be good for a new release of Proxsuite :)

@jcarpent jcarpent merged commit 301fbb9 into Simple-Robotics:devel Jan 13, 2025
75 of 77 checks passed
@fabinsch
Copy link
Collaborator Author

fyi @jberg5: we've done a new release of Proxsuite v0.7.0 in both pip and conda that now ship the solve_no_gil function

@fabinsch fabinsch deleted the topic/gil branch January 22, 2025 14:15
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.

3 participants