-
Notifications
You must be signed in to change notification settings - Fork 140
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
Issue installing dev environment #684
Comments
On 25/02/12 06:53AM, Pierre Kunzli wrote:
Would it be feasible for you to put an `environment.yml` and `environment_cuda.yml` where each package is pinned ? Thank you.
As kraken is used both as a library and an application I can't really
pin everything as it breaks integration with other workflows.
Which OS, hardware,and conda version are you on? With conda 24.11.1 on
amd64 and debian is runs through without issue, so it's possible you're
just not getting a resolvable environment because some dependency isn't
available for your system. Or your conda version is too ancient, they've
played around with that a bit lately (although I see the error comes
from the libmamba solver which points to a recent enough version).
|
One system is a tuxedo OS (based on unbuntu 22.04) and the other a Endeavour OS (Arch based). Some info I get when the error occurs on the tuxedo system. I literally ran this command one hour ago without problem on this system (except the compatibility issue with numpy at runtime).
and the Endeavour OS
|
BTW, what numpy version are you currently using in your dev environment ? should I insist on trying to get numpy < 2 ? Both machines are amd64, forgot to mention it. I will try to use the same conda version as you. |
Looks like it is a bug in libmamba-solver/mamba [0] and has nothing to
do with kraken as such. Either downgrade conda/mamba to a release from
last year or run the pip install.
[0] conda/conda-libmamba-solver#581
|
On 25/02/12 07:32AM, Pierre Kunzli wrote:
BTW, what numpy version are you currently using in your dev environment ? should I insist on trying to get numpy < 2 ?
I'm using numpy 2.0.2. IIRC recent shapely versions need numpy 2.x and
that's a library that has significant numerical differences between
releases so it's better not to mess too much with it.
|
Ok, so now by downgrading conda to 24.11.1 I manage to create the environment, but I run into the issue related to numpy.
Which is weird because it seems I have no other numpy version installed on the system. |
I manage to make it work by bumping scikit-image>=0.25.0 in environment_cuda.yml. Then,
still displays
but ... it works ? Do you think it's a safe way of solving the problem ? So to summarize
Solved my problem |
On 25/02/12 08:28AM, Pierre Kunzli wrote:
I manage to make it work by bumping scikit-image>=0.25.0 in environment_cuda.yml. Then,
```conda list```
still displays
```
scikit-image 0.24.0 pypi_0 pypi
```
conda installs kraken with pip so if the dependencies in setup.cfg are
different than the ones in the environment file it will pull the
dependency from pip and uninstall the conda-sourced one. Unfortunately,
it isn't possible to install pip dependencies in conda envs in no-deps
mode.
but ... it works ?
Do you think it's a safe way of solving the problem ?
Yes, it should be safe. In general, taking a virgin conda env and just
installing kraken with pip in there is going to produce a working
install.
|
Hi, I'm trying to install a development environment of kraken, and ... dependency management is a nightmare...
I'm currently on fd3df08 . I tried this on two computers and had various issues . First, I have a weird bug where
runs into the error
which makes no sense. It occurs sporadically on one system or the other, without a cause I can identify.
Anyway, sometimes the command go through, and end up in a dependency error from conda (don't have one in my history right now), which is extremely verbose and difficult to understand. And off course, sometimes there is the error, sometimes not.
Finally, if the command terminates correctly, I end up with the message
But numpy 2 seems to be incompatible with some other package (error at runtime). So I try to force
In environment_cuda.yml ... and end up with exactly the same message (conda still installs numpy 2.0.2 ...). I tried
numpy<=1.26
as well, with no success.So, following some advices on stackoverflow, I tried mamba instead of conda. By running this command
mamba offers me to install an environment with
Great, so I do this. And when I load the environment, and Python, I get
I don't have a system wide install of numpy. I checked where are the numpy files, they are in the environment created by mamba (or conda). And it's still numpy 2 that is installed.
So, sorry to bother you with that kind of dependency management stuff, and maybe I'm doing something stupid, but do you have any hint to help me ? I'm not an expert with mamba, I suspect it calls conda on the backend, and still installs numpy 2 (but why ?).
Would it be feasible for you to put an
environment.yml
andenvironment_cuda.yml
where each package is pinned ? Thank you.The text was updated successfully, but these errors were encountered: