-
-
Notifications
You must be signed in to change notification settings - Fork 452
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
Drop custom GLPK patch and error handling #37801
Conversation
Documentation preview for this PR (built with commit 5a3698b; changes) is ready! 🎉 |
@mkoeppe are these CI failures a known issue? e.g.
is (AFAICT) eventually causing
|
This one is cosmetic and does not cause failures. Fixed in: |
This one is: Help with figuring out this one would be much appreciated. |
Yes, the doc-html build failure is what causes this. |
By the way, in https://github.com/sagemath/sage/actions/runs/8688244353/job/23823517261?pr=37801#step:11:6372 (for gentoo-python3.11-minimal`) I see a bunch of failures (obviously unrelated to the present PR, of course), including this one:
(There are also a bunch of failures from a different version of Giac but you probably know about this already.) |
OK, let's get rid of it. But why remove |
IIRC it's unused and I only noticed it because I was removing |
But I think we often carry .pxd files that just provide the full API whether it's used or not. |
I would guess that it'd be better to regenerate it however-many years from now based on the latest GLPK, if/when someone wants it. But I don't really care if you think we should keep it. It was removed for housekeeping and not to solve any problem. |
Yes, let's please keep it. (By the way, I don't expect any API developments in GLPK to happen.) |
c798fcf
to
0d451c0
Compare
Easy enough, done. |
By the way, I hope to downgrade GLPK to "optional" soon and replace it by SCIP (see #37494) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks.
Thanks.
GLPK isn't well-maintained these days, and is not exactly at the forefront of mathematical programming, so I think that would be an improvement. |
merge conflict |
There are no longer any "expected crashes" in the GLPK backend, and nothing else seems to be using the glpk.error module. This commit removes it.
SageMath has been carrying a patch to GLPK's error handling that was rejected as unsupported by upstream. The GLPK backend has been updated to obviate this patch (unless the user ignores a warning and changes the default solver...), so we can finally drop it and bring SageMath's GLPK package to parity with the various distributions.
0d451c0
to
5a3698b
Compare
The sage distribution patches GLPK to be able to recover from errors. Upstream rejected this patch, said what it does is unsupported, and no one else has ever adopted it. Sage works fine without it. If someone really wants to add error recovery to GLPK, it has to be done in a way that upstream does not object to. Otherwise, it cannot be done reliably -- no linux distros or conda or homebrew are going to ship our patch. These changes date back to sagemath#29493, and this PR will close sagemath#29829. URL: sagemath#37801 Reported by: Michael Orlitzky Reviewer(s): Matthias Köppe
The sage distribution patches GLPK to be able to recover from errors. Upstream rejected this patch, said what it does is unsupported, and no one else has ever adopted it. Sage works fine without it. If someone really wants to add error recovery to GLPK, it has to be done in a way that upstream does not object to. Otherwise, it cannot be done reliably -- no linux distros or conda or homebrew are going to ship our patch. These changes date back to sagemath#29493, and this PR will close sagemath#29829. URL: sagemath#37801 Reported by: Michael Orlitzky Reviewer(s): Matthias Köppe
The sage distribution patches GLPK to be able to recover from errors. Upstream rejected this patch, said what it does is unsupported, and no one else has ever adopted it. Sage works fine without it.
If someone really wants to add error recovery to GLPK, it has to be done in a way that upstream does not object to. Otherwise, it cannot be done reliably -- no linux distros or conda or homebrew are going to ship our patch.
These changes date back to #29493, and this PR will close #29829.