# Pip installed Python packaged works on PythonSlicer terminal but not on Slicer console

**URL:** <https://discourse.slicer.org/t/pip-installed-python-packaged-works-on-pythonslicer-terminal-but-not-on-slicer-console/41596>\
**Category:** Support\
**Tags:** python, pip\
**Created:** [February 9, 2025, 11:40pm UTC](https://discourse.slicer.org/t/pip-installed-python-packaged-works-on-pythonslicer-terminal-but-not-on-slicer-console/41596 "2025-02-09T23:40:57Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [February 10, 2025, 3:42am UTC](https://discourse.slicer.org/t/pip-installed-python-packaged-works-on-pythonslicer-terminal-but-not-on-slicer-console/41596/4 "2025-02-10T03:42:05Z")

</div>

Reviewing your whl build output, I suspect something to do with HDF5 which I saw was a dependency in your package.

See the following forum post with a similar issue of crashing within the application, but not when calling PythonSlicer directly:

> [@SlicerCAT error with hdf5](https://discourse.slicer.org/t/slicercat-error-with-hdf5/23408/16):
>
> This is only a problem if an application or library brings its own HDF5 as a shared library, without shared library name or symbol mangling. ITK and VTK behave well - their HDF5 will not clash with anything (other than potentially another ITK and VTK), unless you force using “system” HDF5. If you force ITK or VTK to use "system HDF5 then it is entirely up to you to manage version conflicts. I’ve checked the wheel files of netcdf4 and h5py. netcdf4 behaves well - it links HDF5 staticallly, so…

---

_[View the full topic](https://discourse.slicer.org/t/pip-installed-python-packaged-works-on-pythonslicer-terminal-but-not-on-slicer-console/41596)._