On Sat, 2017-01-07 at 07:52 +0000, Gianfranco Costamagna wrote: > > Lumin, can you please check caffe*?
I think caffe-* are safe. Since searching h5py in the upstream code with ack yields the following result (the result is stripped by me): ``` $ ack -i h5py examples/brewing-logreg.ipynb 33: "import h5py\n", 147: "with h5py.File(train_filename, 'w') as f:\n", 156: "with h5py.File(test_filename, 'w') as f:\n", python/requirements.txt 7:h5py>=2.2.0 src/caffe/test/test_data/generate_sample_data.py 6:import h5py 34:with h5py.File(script_dir + '/sample_data.h5', 'w') as f: 39:with h5py.File(script_dir + '/sample_data_2_gzip.h5', 'w') as f: 76:with h5py.File(script_dir + '/solver_data.h5', 'w') as f: ``` HDF5 is just an alternative input data format for Caffe. If users are able to correctly read and write their HDF5 image database with the new version of h5py, then things are expected to go well -- in this case there is nothing to do with caffe-*.
