Library Request: highspy
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start with environment-packages-python.json and check how packages are added to the default, autogluon, and legacy environments. Confirm the supported Python version and package installation process for highspy. Done means import highspy succeeds in a cloud deployment using the relevant environment.
Written by the indexing model from the issue text.
Description
highspy is the official Python interface to the HiGHS mixed-integer/linear optimization solver (MIT licensed). The cloud Python environment already ships HiGHS indirectly through scipy.optimize.milp (environment pins scipy 1.13.1), but that interface rebuilds and re-solves the problem from scratch each call.
highspy exposes the underlying Highs() model object directly, so a caller can keep one model in memory across repeated solves and mutate it incrementally (add cuts, change variable bounds, update costs) instead of resubmitting the full problem every time. That incremental-resolve pattern is needed by algorithms that re-size a mixed-integer program at every rebalance.
Expected behavior
import highspy succeeds in a cloud backtest/live deployment.
Actual behavior
ModuleNotFoundError: No module named 'highspy' - the package is not present in any of the default, autogluon or legacy environments (environment-packages-python.json).
Package details
- PyPI: https://pypi.org/project/highspy/ (latest 1.15.1, manylinux
cp311wheel) - Source: https://github.com/ERGO-Code/HiGHS
- License: MIT
- Dependencies:
numpyonly (already in the environment);typing_extensionsonly on Python < 3.10
Checklist
- I have completely filled out this template
- I have confirmed that this issue exists on the current
masterbranch - I have confirmed that this is not a duplicate issue by searching issues
- I have provided detailed steps to reproduce the issue
Intercom reference: 215476709840912
- Dominant language
- C#
- Stars
- 22.3k
- Forks
- 5.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 52
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from QuantConnect/Lean
-
`LeanData.TryParsePath` fails on an absolute universe file pathPossibly taken @FeiyangP claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QuantConnect/Lean#10005 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
QuantConnect/Lean#9965 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
QuantConnect/Lean#9955 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
QuantConnect/Lean#9953 ·
Maintainers usually reply within 1 day
-
WebullFeeModel charges SPXW options the SPX exchange feeMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
QuantConnect/Lean#9922 · 2 comments ·
Maintainers usually reply within 1 day
All issues in QuantConnect/Lean
Similar issues
-
.NET good first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
HelloblueAI/HelloblueGK#311 ·
Maintainers usually reply within 1 day
-
needs-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
State: Needs Discussion
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/sentry-dotnet#5876 · 1 comment ·
Maintainers usually reply within 1 day
-
area-Extensions-FileSystem untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/runtime#136989 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day