# Issue importing paraview.simple module with Anaconda Prompt

**URL:** https://discourse.paraview.org/t/issue-importing-paraview-simple-module-with-anaconda-prompt/4865
**Category:** ParaView Support
**Tags:** python
**Created:** [July 16, 2020, 8:05pm UTC](https://discourse.paraview.org/t/issue-importing-paraview-simple-module-with-anaconda-prompt/4865 "2020-07-16T20:05:07Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![jclai](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jclai/32/4482_2.png) [@jclai](https://discourse.paraview.org/u/jclai)
#### Post date: [July 16, 2020, 8:05pm UTC](https://discourse.paraview.org/t/issue-importing-paraview-simple-module-with-anaconda-prompt/4865/1 "2020-07-16T20:05:07Z")

</div>

Hello, I am trying to import the paraview.simple module using Anaconda Prompt. I’ve set my system variables (both PATH and PYTHONPATH) to the following:

`C:\Program Files\ParaView 5.8.0-Windows-Python3.7-msvc2015-64bit\bin\Lib\site-packages\win32\libs` (Location of the only .lib file in the whole ParaView 5.8.0-Windows-Python3.7-msvc2015-64bit folder)  
`C:\Program Files\ParaView 5.8.0-Windows-Python3.7-msvc2015-64bit\bin\Lib\site-packages`  
`C:\Program Files\ParaView 5.8.0-Windows-Python3.7-msvc2015-64bit\bin\Lib`  
`C:\Program Files\ParaView 5.8.0-Windows-Python3.7-msvc2015-64bit\bin` (Location of ospray .dll files including ospray\_module\_ispc.dll)

However, I still get this error about 30 times in a row:  
`#osp: INITIALIZATION ERROR --> could not open module lib ospray_module_ispc: The specified module could not be found.`

Someone else is also having the same issue [here](https://discourse.paraview.org/t/could-not-open-module-lib-ospray-module-ispc/4079).

I looked at this [discussion](https://discourse.paraview.org/t/fail-in-importing-paraview-simple-in-python-script/3891) as well as this [one](https://discourse.paraview.org/t/not-able-to-import-paraview-simple-module-on-windows/537/9). The latter said he fixed it by adding a path directly to the .pth file, but I’m not sure how to do this and am not sure if our issue is the same.

---

<div class="post-metadata">

### Author: ![Louis](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/l/ecb155/32.png) [@Louis](https://discourse.paraview.org/u/Louis)
#### Post date: [July 16, 2020, 8:45pm UTC](https://discourse.paraview.org/t/issue-importing-paraview-simple-module-with-anaconda-prompt/4865/2 "2020-07-16T20:45:20Z")

</div>

Hey! Person with this same problem here.

I used this setup to attempt to fix the osprey issue using the .pth file… It um, didn’t work for me, but perhaps it’ll help you!

> **[Modifying Python’s search path with .pth files](https://medium.com/@arnaud.bertrand/modifying-python-s-search-path-with-pth-files-2a41a4143574)**
>
> I’ve just spent the last few hours getting a major headache with this before eventually finding a solution so I wanted to share it with…

If you come up with a solution I’d love to hear what fixes it!

---

<div class="post-metadata">

### Author: ![jclai](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jclai/32/4482_2.png) [@jclai](https://discourse.paraview.org/u/jclai)
#### Post date: [July 16, 2020, 9:08pm UTC](https://discourse.paraview.org/t/issue-importing-paraview-simple-module-with-anaconda-prompt/4865/3 "2020-07-16T21:08:20Z")

</div>

Thanks for sharing! Well, I’m not familiar at all with .pth files and there is an existing one already in the ParaView site-packages folder with this content:

`# .pth file for the PyWin32 extensions`  
`win32`  
`win32\lib`  
`Pythonwin`  
`# Entries needed for a "portable" installations, where the post_install script`  
`# isn't run, which would normally copy the pywin32 core DLL files to either`  
`# the top of the python directory.`  
`# We just stick the source of these DLLs directly on the PATH.`  
`import os;os.environ["PATH"]+=(';'+os.path.join(sitedir,"pywin32_system32"))`

I’m not too sure how to alter it and I’m kind of scared to haha. If you have any ideas please share!