# ParaView internal Python libraries are still broken

**URL:** https://discourse.paraview.org/t/paraview-internal-python-libraries-are-still-broken/3314
**Category:** Development
**Created:** [January 11, 2020, 3:19pm UTC](https://discourse.paraview.org/t/paraview-internal-python-libraries-are-still-broken/3314 "2020-01-11T15:19:26Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [March 20, 2020, 11:49pm UTC](https://discourse.paraview.org/t/paraview-internal-python-libraries-are-still-broken/3314/5 "2020-03-20T23:49:51Z")

</div>

As I mentioned over in [this thread](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/14), the fact that it is looking for `_main` is very odd. Does this still occur today?

---

_[View the full topic](https://discourse.paraview.org/t/paraview-internal-python-libraries-are-still-broken/3314)._