-
Notifications
You must be signed in to change notification settings - Fork 520
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 3.3 #1909
Comments
|
I'm happy to wait. |
@ajelenak said last week (on #1875) that HDF5 1.12.1 would be relased 'soon'. I'm thinking of trying to release h5py 3.3 before that, so that there's a compatible h5py ready to use for anyone upgrading HDF5 straight away. But there's also a case for waiting so that we can test it and upload wheels built with HDF5 1.12.1. Does anyone want to push for that? |
I have lost track of how automated our wheel building process is right now, but if it is not too much work how about doing h5py3.3.0 with hdf5 1.10.x and h5py3.3.1 with hdf5 1.12.1 ? That way we can get wheels out here relatively quickly, but also give people an easy way to back out of the 1.12.1 if they need to. |
The actual building is fully automated on Azure, but to make a release I've been downloading them manually and then uploading them to PyPI. I might wait to see how much pressure there is to do another release with the new HDF5 version. I'm not sure I want to set a precedent that an HDF5 bugfix release automatically means an h5py release, and people can always rebuild h5py if they need a different HDF5 version. But depending on how big the improvements are, it might make sense to do a release relatively soon. |
The release is done 🙂 |
@tacaswell @aragilar I'd like to get 3.3 out soon. Here are some things I'm aware of that I'd like to see finished for that:
[ ] Deprecate 'with dset.astype()' #1842 - deprecate using.astype()
to modify dataset state (to be decided)The text was updated successfully, but these errors were encountered: