Closed GoogleCodeExporter closed 9 years ago
Chances are there are version 1.8.5 HDF5*.DLL files somewhere in your Windows
DLL search path. Or another imported package (e.g. H5py, PyTables) already
loaded conflicting HDF5 DLLs into the process.
Try something like this before importing netCDF4:
import os
from distutils.sysconfig import get_python_lib
os.environ['PATH']=get_python_lib()+';'+os.environ['PATH']
Original comment by cjgoh...@gmail.com
on 13 Dec 2011 at 5:07
You are right.
Appartenly some module I had imported earlier also had imported PyTables.
So right now the story goes like this:
- if I import PyTables before netCDF4 everything goes boom as described.
- if I import netCDF4 first, I can afterwards import PyTables. This does not
complain although I don't know whether it might break something later.
- I can also import h5py without any problems
Your fix doesn't work however, once PyTables was imported.
What I also learned:
- PyTables loads its HDF5 DLL (hdf5dll.dll) from inside its own site-packages
folder
- NetCDF4 loads its HDF5 DLL (hdf5dll.dll) directly from site-packages. This is
the reason why those dlls clash
- h5py loads its DLL also from inside its own site-packages folder but uses a
slightly different name (hdf5dll18.dll), so that it can coexist with the other
two packages.
Therefore, might it be an idea to ask the package maintainers of NetCDF4,
PyTables, h5py etc. to name their dlls with full version appended (like
hdf5dll185.dll)?
Original comment by toromtom...@gmail.com
on 14 Dec 2011 at 6:02
EPD has the same problem btw.
NetCDF4, PyTables, and h5py from http://www.lfd.uci.edu/~gohlke/pythonlibs/ are
all compiled against the same version of HDF.
The proposed fix was meant for situations where conflicting HDF5 dlls exist in
the Windows search path, which is a common problem.
Original comment by cjgoh...@gmail.com
on 14 Dec 2011 at 10:45
Please test using PyTable 2.3.1 and NetCDF4 0.9.8
Original comment by grizzly.nyo
on 19 Dec 2011 at 8:11
Original comment by grizzly.nyo
on 24 Dec 2011 at 6:19
Original comment by grizzly.nyo
on 24 Jan 2012 at 9:24
Original issue reported on code.google.com by
toromtom...@gmail.com
on 13 Dec 2011 at 10:04