Closed duncanwp closed 8 years ago
I see a mixture of channels there that worries my. One is the Scitools channel and the other is the weird netcdf4 1.2.4 np111py27_2 condo-forge
. That should be conda-forge
:confused: (Maybe it is just an alias from when you added the channel... Not sure.)
Can you issue the following commands for me so we can debug this further:
conda create -n TEST -c conda-forge netcdf4 --yes
source activate TEST
python -c "import netCDF4; print(netCDF4.__version__)"
and if that does not work send us the results of:
conda list > debug.txt
conda info >> debug.txt
Thanks!
Edit: BTW I tried with your requirements file and the .condarc
below and everything worked fine on Linux. It is either an issue on OS X
or a bad mix of channels. The results above will help us sort this out.
> cat ~/.condarc
channels:
- conda-forge
- defaults
show_channel_urls: true
Great, thanks. OK so the TEST environment worked fine - it picked up version 1.1.1 and linked against the OS libjpeg 8d.
Yes, it only seems to be a problem on OSX, and I'm wondering if it's because of the built-in libjpeg library?
This is the result with the above .condarc file: debug.txt. It's still picking up some sci-tools packages - I must have them installed in my root env - but I don't think there's anything there that should mess with the NetCDF dependency resolution.
but I don't think there's anything there that should mess with the NetCDF dependency resolution.
The dependency tree might play tricks with us and it is hard to follow it sometimes, but jasper depends on jpeg
and scitools does not pin the jpeg
version. Which means that you have some packages, like hdf4
which is a dependency of netcdf4
, compiled against jpeg 9*
and conda is play loose with that pin because other packages you are installing are not pinned.
In theory you do not need the scitools channel at all when using conda-forge b/c everything that exists there also exists in conda-forge
. I strongly recommend you to reduce the number of channels, the more you mix the more conflicts like that you will get.
Since the problem is not in conda-forge I am closing this, but we can keep discussing this until we solve your problem.
Perfect, thanks for that - I was struggling to understand why conda wasn't picking the right library. I've built a clean environment with only condo-forge libraries and all is working as expected.
Thanks again
Glad it is resolved!
Doing a clean install of these dependencies using the condo-forge channel gives incompatible libraries:
These are the libraries conda picks up:
The weird thing is that I have libjpeg 9 installed, so for some reason it looks like the netcdf install isn't linking against it?