Avoid setting up an explicit python path on shogun
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- build-system
Research direction
Start with libraries/shogun_install.sh at the linked CMake configuration around line 31, and compare its Python path settings with an active virtualenv. Remove or revise the explicit PYTHON_INCLUDE_DIR, PYTHON_EXECUTABLE:FILEPATH, and PYTHON_PACKAGES_PATH settings so the active environment can be used, then verify that Shogun installation finds its Python dependencies.
Written by the indexing model from the issue text.
Description
On shogun install file, when the user is using, e.g: virtualenv, this kind of CMAKE configuration will override the users configuration for python environment.
Is it really necessary? In my case, the system-wide python didn't have numpy, but my active virtualenv had and it was not finding it. By removing the definition of PYTHON_INCLUDE_DIR, PYTHON_EXECUTABLE:FILEPATH and PYTHON_PACKAGES_PATH variables it worked as expected.
- Dominant language
- Python
- Stars
- 107
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 mlpack/benchmarks
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
mlpack/benchmarks#146 · 5 comments · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mlpack/benchmarks#145 · 1 comment ·
-
question
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mlpack/benchmarks#144 · 8 comments ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
mlpack/benchmarks#143 · 3 comments · 4 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
mlpack/benchmarks#139 ·
All issues in mlpack/benchmarks
Similar issues
-
[BUG] Container scenario crashes without expected_recovery_time, kube DNS example uses retry_waitOpenneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
krkn-chaos/krkn#1627 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NousResearch/hermes-agent#136483 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
[BUG] LazyStackedTensorDictStore zeroes the last byte of a new key set on the last elementPossibly taken @peterdsharpe claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pytorch/tensordict#2307 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day