Swmr Capability Of Hdf5 And Therefore Also Of H5py
I am suffering from a shortcoming of h5py its swmr (single write multiple read) capability as described in an issue on github. The issue is labelled with 'bug-in-external-lib' which suggests that the shortcoming is located at the underlying hdf5 library rather than in h5py itself. I wonder if there is any interest from the hdf5 maintainers to change that. Hdf5 has a bitbucket repository with a branch called 'full_swmr'. Does anybody know how mature this branch is? Is there a chance to see full swmr in hdf5 in the nearer future?
I also posted the question in the HDF5 group forum and just got a reply that includes answers to both of my questions (thank you Elena).
Concerning the first question: the 'full_swmr' branch is stable but it does not resolve the mentioned github issue. Concerning the second question: the HDF5 Group is interested in achieving full swmr support. In fact they started to work on a implementation to provide exactly that. This implementation will also resolve the github issue mentioned in the question above. To my understanding the HDF5 Group just kicked the project off and it is not yet foreseeable when the implementation will be made public.
- → What are the pluses/minuses of different ways to configure GPIOs on the Beaglebone Black?
- → Django, code inside <script> tag doesn't work in a template
- → React - Django webpack config with dynamic 'output'
- → GAE Python app - Does URL matter for SEO?
- → Put a Rendered Django Template in Json along with some other items
- → session disappears when request is sent from fetch
- → Python Shopify API output formatted datetime string in django template
- → Shopify app: adding a new shipping address via webhook
- → Shopify + Python library: how to create new shipping address
- → shopify python api: how do add new assets to published theme?
- → Access 'HTTP_X_SHOPIFY_SHOP_API_CALL_LIMIT' with Python Shopify Module