[Yt-dev] h5py bug
matthewturk at gmail.com
Mon Apr 11 17:22:22 PDT 2011
I am generally opposed to upgrading either Matplotlib or h5py without
a very careful and detailed study of how the API changes. The
transition between 1.1 and 1.2 of h5py included a number of API
breakages that affected us, and we saw the same thing with 0.9x to
0.9 and now 1.0 to 1.0.1 in matplotlib.
Have you identified the smallest possible set of code that replicates
this, as you called it, apparent bug? Did you test it against 1.3.1?
Please also consider reporting it upstream.
On Mon, Apr 11, 2011 at 8:08 PM, Stephen Skory <s at skory.us> wrote:
> Hi all,
> 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?
> Stephen Skory
> s at skory.us
> 510.621.3687 (google voice)
> Yt-dev mailing list
> Yt-dev at lists.spacepope.org
More information about the yt-dev