> I've just encountered the same h5py bug in another place. This is with > h5py 1.2.0. The newest is 1.3.1. What do we think about upgrading? As a follow-up, I just tried things with 1.3.1, and I didn't get the crash. -- Stephen Skory s at skory.us http://stephenskory.com/ 510.621.3687 (google voice)