silx view: Fixed ensure hdf5 file locking is disabled

[t20100]

• The PR title is formatted as: <Module or Topic>: <Action> <Summary> (see contributing guidelines)

PR summary

Set HDF5_USE_FILE_LOCKING before importing hdf5plugin.

related to #4594
partly revert #4376

AI Disclosure

• No AI used

[t20100]

Add preparation of a release.

I propose to make a minor release since there is no new features. The only questionable PR for me is #4560 which adds some typing.

[loichuder]

Is it possible to add a test to avoid this in the future?

[t20100]

Is it possible to add a test to avoid this in the future?

Yes! I leave issue #4594 opened to add a non regression test, I prefer not to delay the bug fix release.

[woutdenolf]

@sergey-yaroslavtsev To be checked that pymca has the same issue.

[sergey-yaroslavtsev]

@sergey-yaroslavtsev To be checked that pymca has the same issue.

Locking should be set before importing hdf5plugin and h5py. No sure why but it is so.
I think it is OK in PyMca now:
1st was introduced silx-kit/pymca#1198 (_init_hdf5() in PyMcaAppInit.py)
2nd was fixed in silx-kit/pymca#1209

[t20100]

Locking should be set before importing hdf5plugin and h5py. No sure why but it is so.

Now, libhdf5 look at the locking environment variable once when it is loaded.

This issue was only affecting silx view.

[payno]

Maybe we could add some comment on the code linking to this issue in order to avoid reproducing it ? (because personally in 2 months I will have forgot :( )