Add support for HDMF 2.3

[rly]

Motivation

HDMF 2.3 introduces a few changes. This PR addresses those changes and updates the requirements to require hdmf >= 2.3.

Checklist

• Have you checked our Contributing document?
• Have you ensured the PR description clearly describes problem and the solution?
• Is your contribution compliant with our coding style? This can be checked running flake8 from the source directory.
• Have you checked to ensure that there aren't other open Pull Requests for the same change?
• Have you included the relevant issue number using #XXX notation where XXX is the issue number?

[bendichter]

@rly this also add support for 3.0?

[ajtritt]

@rly this also add support for 3.0?

No, h5py 3.x support is not complete. It will likely be non-backward compatible

[bendichter]

@ajtritt ok. I'm trying to test out hdmf enh/h5py 3.x with pynwb and nwbwidgets. Would I have to take those changes and apply them to hdmf 2.3? Then use this branch of pynwb (or dev once it's merged)?

[bendichter]

It appears I got confused between the different packages. I thought there was an HDMF 3.0, but I was probably confusing that with the h5py 3.0 support.

[rly]

We were initially planning to release HDMF as version 3.0 but the breaking changes were not so important and support for h5py 3.x would be another breaking change, so we decided to pull the breaking changes out of the just-released release (2.3) and save them for an upcoming release that supports h5py 3.x.

[bendichter]

We were initially planning to release HDMF as version 3.0 but the breaking changes were not so important and support for h5py 3.x would be another breaking change, so we decided to pull the breaking changes out of the just-released release (2.3) and save them for an upcoming release that supports h5py 3.x.

Thanks, this makes perfect sense and clarifies my confusion.