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
Eliminate compatibility mode from HDF5 I/O #8899
Eliminate compatibility mode from HDF5 I/O #8899
Conversation
Thanks! I don't use HDF5, so I cannot comment. 😬 |
Please remove changes to the helpers. I don't use hdf5 files so don't know how widely the old formats are used, and what the actual issue with it. Naively I would say we should be able to read in as many types of files as possible, but should not write non standard or obsolete versions of them. |
43f4881
to
bc512e8
Compare
Oh, sorry for the helpers thing. Done |
bc512e8
to
86ffc83
Compare
@bsipocz the main problem I see is that the old reader now remains untested because we have no way to write old-format files. Besides that, I would also prefer to keep as many formats as possible |
Re: testing old format reader -- Is it possible to write it out now while we can and store it as a test data file (either remote or local depending on file size and your philosophy about data files). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with removing this, and also agree with @pllim's suggestion - we should basically take the example from the first half of test_preserve_serialized_compatibility_mode
, write it out as a file, store it with the data files for tests (inside a data
directory), and use it to continue to test the reading. I think the file will be very small, so I'm not worried about it, and we shouldn't have to change it in future since it's just a legacy format.
@matteobachetti - could you rebase, to get rid of the merge commits? |
b69778e
to
50add74
Compare
@astrofrog: done, but 32-bit tests are falling and I'm not sure why |
Oh, I see the likely problem with the 32-bit build: #8934 |
@matteobachetti - yes, failures should be unrelated. Given that this needs a rebase anyway due to the unrelated commit, I would say rebase after #8945 (or alternative) is merged. |
Oh, I wonder why that commit is there at all. I already rebased in theory O_o. |
@matteobachetti - the workaround in merged, so you can rebase. You can manually remove the commit if you rebase in interactive mode. |
50add74
to
718883c
Compare
@bsipocz rebased and dropped commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review comments have been addressed.
Thanks @matteobachetti |
As per #8888
@taldcroft, @pllim, @astrofrog, @bsipocz et al.: is there a use case for being able to still read the old format?