-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add build requirements in pyproject.toml #10
base: lkh-3
Are you sure you want to change the base?
Conversation
This allows pip to pick up and install scikit-build before running setup.py, thereby avoiding the "No module named 'skbuild'" error. Also include the wheel package, needed to build wheels.
[I hereby commit to uploading a sdist and taking a look at this tomorrow or Monday] |
Great, thanks! |
I managed to get Now I decided to fully port the new LKH version: from 2.0.9 to 3.0.8 and I'm fixing some linker stuff. The |
Thanks for this! I compared v0.1.2 and v0.1.3 on a small dataset containing 200 random 2-D point, i.e. the distance matrix has dimensions 200 x 200. By the way, 0.1.3 seems like a very minor change for a package that had a major version bump on its internal library :-) Both found the same path: I was curious about that bit on the lower left where the path crosses itself, which seems suboptimal, but that could just be poor intuition on my side... I then tried to time both, since the new one seemed faster. v0.1.2 took 4.6 seconds, but v0.1.3 crashed when I ran it twice on the same data:
Elkai 0.1.2 does not have this issue (built on macOS 11.7.3, Python 3.10, scikit-build 0.16.7). |
I will probably do a major version bump! The branch and the PR don't mention an explicit elkai version - even though I did increment the patch version. Should we do 1.0.0? Thanks for the bug report, memory issues are part of the pending PR. I'm almost certain that multiple calls to solve will leak, but also free extra memory. I'm also planning on adding a patch file instead of committing to the LKH folder (that removes their printfs and some allocations) so that the LKH folder stays true to upstream. |
12d8812
to
fbb29ea
Compare
@ludwigschwardt Have you tried the new elkai? |
This allows pip to pick up and install scikit-build before running setup.py, thereby avoiding the "No module named 'skbuild'" error. Also include the wheel package, needed to build wheels.
This should allow pip to build elkai 0.1.2 from source from PyPI for systems without prebuilt wheels (once the source distribution is uploaded 🙂).