# ParaView 5.7 doesn't work scipy internal python module

**URL:** https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267
**Category:** Development
**Tags:** python
**Created:** [January 6, 2020, 6:24am UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267 "2020-01-06T06:24:03Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![MBG](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/m/7ab992/32.png) [@MBG](https://discourse.paraview.org/u/MBG)
#### Post date: [January 13, 2020, 5:25pm UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/13 "2020-01-13T17:25:24Z")

</div>

Maybe the issue is not so important if we will have soon ParaView 5.8 with Python 3:

> [@ParaView w/ Python 3 on Mac - when?](https://discourse.paraview.org/t/paraview-w-python-3-on-mac-when/3083/10):
>
> pvpython is just python with the correct PYTHONPATH and LD\_LIBRARY\_PATH passed in. Using a separate executable spares the user of knowing where the python modules and libraries are in the ParaView install or build hierarchy. There is another more subtle differences because python has all functionality built in while pvpython accesses the python functionality through dynamic libraries but it would work the same most of the time.

---

_[View the full topic](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267)._