# Build paraview with python 3.7.3 but ModuleNotFoundError: No module named ‘vtkmodules.vtkCommonCorePython’

**URL:** https://discourse.paraview.org/t/build-paraview-with-python-3-7-3-but-modulenotfounderror-no-module-named-vtkmodules-vtkcommoncorepython/1928
**Category:** ParaView Support
**Created:** [May 26, 2019, 1:15pm UTC](https://discourse.paraview.org/t/build-paraview-with-python-3-7-3-but-modulenotfounderror-no-module-named-vtkmodules-vtkcommoncorepython/1928 "2019-05-26T13:15:18Z")
**Posts on this page:** 1
**Page:** 2

<div class="post-metadata">

### Author: ![rogezy](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/r/71c47a/32.png) [@rogezy](https://discourse.paraview.org/u/rogezy)
#### Post date: [October 9, 2019, 7:49am UTC](https://discourse.paraview.org/t/build-paraview-with-python-3-7-3-but-modulenotfounderror-no-module-named-vtkmodules-vtkcommoncorepython/1928/21 "2019-10-09T07:49:50Z")

</div>

Hi all,

this discussion has helped me indirectly and maybe my case will give you some indication on similar issues… I was updating my build process to ParaView 5.7 on Windows (ouch! a bunch of modifications but hopefully I get to an end now…), and on execution I had this vtkCommonCorePython lib not found, even using pvpython with all PYTHONPATH & PATH well defined.

I ran depends.exe on vtkCommonCorePython.pyd and realized that it was depending on the debug version of VTK DLLs. In fact, when building ParaView, I firstly built the Release, then the Debug and doing so, the site-packages python libs where replaced by debug ones. Rebuilding the Release afterwards fixed all this.

Hope this could help…

Yves

[Previous page](https://discourse.paraview.org/t/build-paraview-with-python-3-7-3-but-modulenotfounderror-no-module-named-vtkmodules-vtkcommoncorepython/1928.md?page=1)