-
Notifications
You must be signed in to change notification settings - Fork 128
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
Installation failing due to shapely=2.0.0 (linux64) issue #2965
Comments
looking into this now 👍 |
Note that this is during the Julia install, i.e. I think it is the Conda environment that Julia creates inside the Julia environment inside our Conda environment. Ceterum censeo... |
Per aspera ad arseum - it is indeed Julia, and its slowness adapting to new deps - the new shapely=2.0 was released less than 2 days ago, right when we started seeing this problem |
what do you think @zklaus - pin shapely<2.0? 1.8.5 works well with the current julia we have (1.8.3). Maybe raise this with Julia conda feedstock admins too? |
Pin how? This is somehow getting pulled in by one of the packages in |
yes, add shapely=1.8.5 (or whatevs the hash etc) in the Project toml - or just ping the good ole Julia package maintainers @ngam and @mkitti and see what they say? |
What do we need from the Julia feedstock? A rebuild? |
I think it's also possible to tell Julia to use the existing conda environment instead of creating its own. Wouldn't that be easier? |
If the Julia feedstock activate script is working properly, this should not be happening. Via environment variables, Julia should be used to use the existing conda environment. https://github.com/conda-forge/julia-feedstock/blob/main/recipe/scripts/activate.sh |
very many thanks @mkitti - that pointer to get Julia to use the current conda env is defo a great idea! I do, however, I feel a bit embarrassed for pinging you good folk, before I recreate the issue locally, and I just did that and found this fail has nothing to do with Julia, see below @bouweandela @zklaus
This needs to be tackled internally in esmvalcore or we have to raise it with Shapely if it's their problem. Sorry @mkitti and @ngam - cheers for your help and happy holidays 🎄 |
in fact, that error pops up everytime an instance of esmvaltool is called, even for |
but looking at what I have in my env:
|
Opened this conda-forge/shapely-feedstock#121 |
and closed it too, after having actually seen the shapely conda forge pkg tests that are correct and pass for linux64, and, more importantly all is fine with our esmvalcore entry points in |
OK some systematic progress wrt this:
All these things imply that one or more deps of only esmvaltool (and not of esmvalcore) that depend on shapely is/are causing this (or, in the worst case scenario one or more deps of those FMW); the list od deps that use shapely as dep from esmvaltool is the following, cross-correlated to esmvalcore deps: "Core" means it's also an esmvalcore dep, "NOT Core" means it's not:
Am gonna have a closer look at "NOT Core" ones, fortunately they're not many... |
GAH! All this time and the answer was right under my nose and due to informational bias I didn't even think of checking - it's our esmvalcore=2.7.1 package, specifically setup.py off the v2.7.x branch - it needs |
The installation tests are failing because of an incompatibility with shapely. See here for an example. Stack trace:
Also an example from our Github Actions test suite where it's a bit easier to see what deps get in the env etc
The text was updated successfully, but these errors were encountered: