Hi Chris,
> Issue 240 has our lab's software crashing more often than I'd like, and
> so I'm trying to upgrade to h5py 2.1.0 where the issue is fixed. I can
> verify that under linux the issue is no more, but unfortunately I'm stuck
> with Windows in the lab.
Ouch. Sorry about this; 2.1.0 is way behind schedule and building
h5py on Windows is seriously frustrating.
> python setup.py build --hdf5="C:\Program Files\HDF Group\HDF1.8.9"
> --compiler=msvc
This looks right (although you shouldn't have to force the compiler option).
> Any idea what I'm doing wrong? Where do I have to put the dlls for them to
> be found by h5py? I've tried putting them in python's site-packages, but it
> doesn't seem to help. I don't care about compression at all, and haven't
> tried to include zlib.
All the dlls should go in the "h5py" directory (where all the .pyx
files are); Windows finds them when h5py is imported. However, if
you're using the HDF Group builds I think you'll also have to provide
both zlib and szip libraries or the import will fail.
> Alternately, an eta on the release of 2.1.0 would help me decide whether
> this is worth pursuing, because I can possibly live with my program crashing
> until then!
The best I can say at the moment is 2.1.0-beta will be coming out
"soon" (meaning a few weeks). We made some changes in 2.1.0 that got
away from me and led to lots of regressions, and I haven't had the
time recently to get them all nailed down. There are lots of bugfixes
in 2.1.0 that people are waiting on (as you discovered). :/
Andrew