# h5py support in ParaView

**URL:** https://discourse.paraview.org/t/h5py-support-in-paraview/2638
**Category:** Development
**Tags:** python
**Created:** [September 27, 2019, 11:48am UTC](https://discourse.paraview.org/t/h5py-support-in-paraview/2638 "2019-09-27T11:48:45Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Loic](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/l/e9c0ed/32.png) [@Loic](https://discourse.paraview.org/u/Loic)
#### Post date: [September 27, 2019, 11:48am UTC](https://discourse.paraview.org/t/h5py-support-in-paraview/2638/1 "2019-09-27T11:48:45Z")

</div>

Hi,

I need to develop some custom filters to manipulate data stored in a HDF5 file.  
I’ve seen a very interesting [post on Kitware Blog](https://blog.kitware.com/developing-hdf5-readers-using-vtkpythonalgorithm/) on that subject.  
It seems that this receipt cannot work with current official ParaView package: it uses the h5py module which currently in not available in these packages.

A ticket to add [h5py support in Paraview binairies](https://gitlab.kitware.com/paraview/paraview/issues/17314) has been open two years ago. Does anybody know if there is some work in progress on that issue?

I’ve also seen a receipt to [build h5py with paraview](https://github.com/Exteris/paraview-python-file-reader) but it seems a bit outdated. Does anybody has an updated receipt working with ParaView 5.6 or 5.7, Python 3 and some hints to make it works for linux and windows ?

Thanks in advance,

## Regards,

Loic

---

<div class="post-metadata">

### Author: ![utkarsh.ayachit](https://discourse.paraview.org/user_avatar/discourse.paraview.org/utkarsh.ayachit/32/39_2.png) [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [September 27, 2019, 12:34pm UTC](https://discourse.paraview.org/t/h5py-support-in-paraview/2638/2 "2019-09-27T12:34:56Z")

</div>

> [@Loic](#):
>
> A ticket to add [h5py support in Paraview binairies](https://gitlab.kitware.com/paraview/paraview/issues/17314) has been open two years ago. Does anybody know if there is some work in progress on that issue?

It is indeed on the wish list, but is potentially a non-trivial fix. Such issues tend to get deferred until there’s some funding available to work on it.
