Update lpsolve builds #14
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Compatible with python 2.7 and 3.x
5.5.1 version has updates to reset the signal handlers
amarkpayne
force-pushed
the
update_lpsolve_builds
branch
from
d6de3fb
to
53efacc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In anticipation of the upgrade to python 3, I have updated the conda-build recipe both for lpsolve (the shared C library) and lpsolve55 (the wrapper for python). I was able to find a repository online (https://github.com/chandu-atina/lp_solve_python_3x) that modified the source files for these packages to make them compatible for building with python 2 or 3. I forked this repository (https://github.com/amarkpayne/lp_solve_python_3x) so that I could make a couple of needed changes to make the builds work. The original author of this repository has uploads on conda-forge for these packages, but the python 2 build results in segmentation faults (perhaps do to the same reason why I had to make changes to this repo?), so for now I think it is best to use our own builds.