# Paraview conflicting with local Python installation

**URL:** https://discourse.paraview.org/t/paraview-conflicting-with-local-python-installation/16582
**Category:** Development
**Created:** [May 7, 2025, 1:54pm UTC](https://discourse.paraview.org/t/paraview-conflicting-with-local-python-installation/16582 "2025-05-07T13:54:19Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![ar505](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/a/e68b1a/32.png) [@ar505](https://discourse.paraview.org/u/ar505)
#### Post date: [May 7, 2025, 1:54pm UTC](https://discourse.paraview.org/t/paraview-conflicting-with-local-python-installation/16582/1 "2025-05-07T13:54:19Z")

</div>

I have a case where I cannot run paraview server manager commands from Python Shell in Paraview where there is local Python installation. When I load a case and enter the command GetActiveSource() , it will fail. If I rename the local installation site packages folder, everything works fine. Is there a way to exclude the local site module from the Python Shell sys.path so that this conflict will not occur?  
Thanks

---

<div class="post-metadata">

### Author: ![nicolas.vuaille](https://discourse.paraview.org/user_avatar/discourse.paraview.org/nicolas.vuaille/32/5873_2.png) [@nicolas.vuaille](https://discourse.paraview.org/u/nicolas.vuaille)
#### Post date: [May 14, 2025, 1:29pm UTC](https://discourse.paraview.org/t/paraview-conflicting-with-local-python-installation/16582/2 "2025-05-14T13:29:58Z")

</div>

For reference, it looks similar to this reported issue: [https://gitlab.kitware.com/paraview/paraview/-/issues/22384](https://gitlab.kitware.com/paraview/paraview/-/issues/22384)

From `pvpython`, it suggests to run it with `-S` option. But for `paraview` no better idea than your workaround.