We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Independent of #24824, sage shouldn't check for the exact glpk version in the doctests.
I'm using sage with glpk 4.65 with the debian patch to ignore the warnings for now and noticed that this doctest checks for glpk 4.63.
Component: distribution
Author: Timo Kaufmann
Branch/Commit: 89d068d
89d068d
Reviewer: Vincent Delecroix
Issue created by migration from https://trac.sagemath.org/ticket/25329
The text was updated successfully, but these errors were encountered:
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
Don't check for the exact glpk version
Sorry, something went wrong.
Changed commit from 70ebe92 to 89d068d
70ebe92
Changed branch from u/gh-timokau/glpk-version-check to 89d068d
cc51e6f
No branches or pull requests
Independent of #24824, sage shouldn't check for the exact glpk version in the doctests.
I'm using sage with glpk 4.65 with the debian patch to ignore the warnings for now and noticed that this doctest checks for glpk 4.63.
Component: distribution
Author: Timo Kaufmann
Branch/Commit:
89d068d
Reviewer: Vincent Delecroix
Issue created by migration from https://trac.sagemath.org/ticket/25329
The text was updated successfully, but these errors were encountered: