-
Notifications
You must be signed in to change notification settings - Fork 9
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
Unable to install pyklb #11
Comments
I've also tried installing by cloning the repository, and then running
|
Hi @jmmuncie, I'm facing the same issue today. What's your setup (OS, version, ...)? From your log, it looks like you're running Python 3.8. Frustratingly enough, back in July 2023, the installation instruction ( I had to create a fresh new virtual environment for May I ask what your use case is for installing Back in July 2023, I was running Python 3.9 system-wide. In October 2023, I upgraded my setup to 3.10 because of (thanks to) SPEC 0. Aww, I should have expected problems with research code, which is typically (regrettably but understandably) not really maintained... Nonsense, you will say, since virtual environments are precisely meant to pin package versions. Of course, I think I messed up: I remember 'forcing' Python 3.10 'everywhere' because, even after it was properly installed, my default (system-wide) Python would still point to some Python 3.9; I believe that's because I have Conda, Miniconda, Mamba, and too much clutter in my paths, symlinks, ... There must be conflicts somewhere with all these Python layers. For example, here's something weird: (base) marianne@mkcor:~/Work$ python --version
Python 3.10.0
(base) marianne@mkcor:~/Work$ which python
/home/marianne/mambaforge/bin/python
(base) marianne@mkcor:~/Work$ python3.9 --version
Python 3.9.15
(base) marianne@mkcor:~/Work$ which python3.9
/home/marianne/mambaforge/bin/python3.9
(base) marianne@mkcor:~/Work$ python3.9 -m venv ~/.virtualenv/pyklb/
(base) marianne@mkcor:~/Work$ source ~/.virtualenv/pyklb/bin/activate
(pyklb) (base) marianne@mkcor:~/Work$ python --version # WHAT???
Python 3.10.0
(pyklb) (base) marianne@mkcor:~/Work$ which python
/home/marianne/.virtualenv/pyklb/bin/python
(pyklb) (base) marianne@mkcor:~/Work$ /home/marianne/.virtualenv/pyklb/bin/python --version
Python 3.9.15
Now it makes me pretty anxious to realize that venvs are not as isolated as they 'should' be(?); today, when I activated my "Jul 19, 2023" venv, I couldn't import In my normal practice, I create and re-create venvs whenever, since all I need is the requirements file... From the error log, it looks like this project (pyklb) is just missing the new style of source tree based around Thanks for reading my rant, |
I think I managed it. Here's what I did: micromamba create -n trypyklb python=3.9
micromamba activate trypyklb
git clone https://github.com/bhoeckendorf/pyklb.git
cd pyklb
git switch skbuild I'm using micromamba to get access to Python 3.9 but use pip from then on. There's a Patch
Safe below to From a3319dec03aa7997b107d217a336d10779e6aa15 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lars=20Gr=C3=BCter?= <[email protected]>
Date: Thu, 25 Jan 2024 13:14:02 +0100
Subject: [PATCH] Pin dependencies
---
pyproject.toml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pyproject.toml b/pyproject.toml
index 3d25ae5..e60aca5 100755
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -1,2 +1,2 @@
[build-system]
-requires = ["cmake", "cython", "numpy", "setuptools", "scikit-build", "wheel"]
+requires = ["cmake==3.20.4", "cython==0.29.23", "numpy==1.21.0", "setuptools==57.0.0", "scikit-build==0.11.1", "wheel"]
--
2.43.0
Then I simply ran |
Thanks a lot @lagru! In the meantime, I had been able to use pre-compiled libraries from a collaborator that worked with my system, but it's great to have a more generalizable solution. Thanks for sharing! |
Hi,
I am trying to install pyklb using
pip install git+https://github.com/bhoeckendorf/pyklb.git@skbuild
And get a very long error message:
Any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered: