I’ve opened a question of whether h5py should disable writing object timestamps by default.
There are more details there, but to summarise: There’s a clear, albeit niche, use case where you don’t want timestamps, if you want to be able to generate byte-for-byte equal HDF5 files. But it’s not obvious how to get any timestamps from h5py, or with the HDF5 command line tools (h5ls, h5dump, h5stat). And the docs for H5Oget_info3 say that only ctime is implemented anyway. And, going by discussions here and on h5py, it looks like no-one cares much about these limitations - maybe because timestamps aren’t used much.
But maybe I’m missing something? If there’s some use case where the timestamps that are implemented are useful, and the existing ways to access them are sufficient, I’d like to know, so we can weigh that up against the use case where we know timestamps are a nuisance.