# Import paraview (5.8.1) module in Python 3.7 on Anaconda Juypter notebook using MacOS
**URL:** https://discourse.paraview.org/t/import-paraview-5-8-1-module-in-python-3-7-on-anaconda-juypter-notebook-using-macos/5928
**Category:** ParaView Support
**Tags:** python
**Created:** [November 29, 2020, 8:13pm UTC](https://discourse.paraview.org/t/import-paraview-5-8-1-module-in-python-3-7-on-anaconda-juypter-notebook-using-macos/5928 "2020-11-29T20:13:57Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@fatraphael95](https://discourse.paraview.org/u/fatraphael95)
#### Post date: [November 29, 2020, 8:13pm UTC](https://discourse.paraview.org/t/import-paraview-5-8-1-module-in-python-3-7-on-anaconda-juypter-notebook-using-macos/5928/1 "2020-11-29T20:13:57Z")
Hello,
I have a python script that I am attempting to run in Anaconda Juypter Notebook using MacOS Catalina.
On a line that tries to import Paraview that says:
“from paraview.simple import \*”
An error occurs that says:
“No module named ‘paraview’”
I’m really new to ParaView and Python as I am not too sure how to set the paths as stated in some of the topics. Or When typing out “pvpython” onto the terminal, this was what I got from the terminal as stated below.
(base) raphaels-mbp-2:~ Raphael$ python
Python 3.6.5 (default, Aug 23 2020, 11:53:50)
[GCC 4.2.1 Compatible Apple LLVM 11.0.3 (clang-1103.0.32.62)] on darwin
Type “help”, “copyright”, “credits” or “license” for more information.
> > > pvpython
> > > Traceback (most recent call last):
> > > File “”, line 1, in
> > > NameError: name ‘pvpython’ is not defined
Lastly, I have tried following the steps as shown in this link below:
Link: [https://gitlab.kitware.com/paraview/paraview/blob/master/Documentation/dev/build.md#complete-compilation-guide](https://gitlab.kitware.com/paraview/paraview/blob/master/Documentation/dev/build.md#complete-compilation-guide)
However, when typing “`git submodule update --init --recursive`”, this was the error I got on the terminal.
git-lfs filter-process: git-lfs: command not found
fatal: The remote end hung up unexpectedly
Unable to checkout ‘f2aa6ad5be1a97e3fb41ef4680ee2c76c3434ac0’ in submodule path ‘VTK/ThirdParty/vtkm/vtkvtkm/vtk-m’
Failed to recurse into submodule path ‘VTK’
Really not sure what to do and how to resolve this issue. Currently, I know I have the anaconda platform installed (Using Juypter Notebook) along with ParaView v5.8.1.
Do kindly hope someone could help me with this as I am trying my best to understand how this works.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [May 15, 2021, 6:31pm UTC](https://discourse.paraview.org/t/import-paraview-5-8-1-module-in-python-3-7-on-anaconda-juypter-notebook-using-macos/5928/2 "2021-05-15T18:31:58Z")
> [@fatraphael95](#):
>
> Or When typing out “pvpython” onto the terminal, this was what I got from the terminal as stated below.
`pvpython` is an executable, not a command to be run inside of a `python` shell.
> [@fatraphael95](#):
>
> However, when typing “`git submodule update --init --recursive`”, this was the error I got on the terminal.
>
> git-lfs filter-process: git-lfs: command not found
You’ll need to install [`git-lfs`](https://git-lfs.github.com/) to download VTK-m’s testing data.
---
### Author:  [@baysalse](https://discourse.paraview.org/u/baysalse)
#### Post date: [August 25, 2022, 5:16pm UTC](https://discourse.paraview.org/t/import-paraview-5-8-1-module-in-python-3-7-on-anaconda-juypter-notebook-using-macos/5928/3 "2022-08-25T17:16:37Z")
I know it’s been a long time since you asked this question. However, I faced the almost same problem when I tried to download source code by following instructions in [ParaView:Build And Install](https://www.paraview.org/Wiki/ParaView:Build_And_Install#Download_And_Install_CMake) and thought it might be helpful for others. The steps I followed are:
1. brew install git-lfs
2. cd paraview
3. git clone --recursive [https://gitlab.kitware.com/paraview/paraview.git](https://gitlab.kitware.com/paraview/paraview.git)
4. git submodule update --init --recursive
5. …
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [August 29, 2022, 1:32am UTC](https://discourse.paraview.org/t/import-paraview-5-8-1-module-in-python-3-7-on-anaconda-juypter-notebook-using-macos/5928/4 "2022-08-29T01:32:53Z")
Hi @baysalse ,
This guide is out of date, please here: [https://gitlab.kitware.com/paraview/paraview/-/blob/master/Documentation/dev/build.md](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Documentation/dev/build.md)
Also, ParaView do not use git-lfs at all.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [September 7, 2022, 9:15pm UTC](https://discourse.paraview.org/t/import-paraview-5-8-1-module-in-python-3-7-on-anaconda-juypter-notebook-using-macos/5928/5 "2022-09-07T21:15:40Z")
> [@mwestphal](#):
>
> Also, ParaView do not use git-lfs at all.
Only if you ignore the VTK-m nested submodule. But it is part of the recursive git repo, so it can be necessary.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 8, 2022, 6:29am UTC](https://discourse.paraview.org/t/import-paraview-5-8-1-module-in-python-3-7-on-anaconda-juypter-notebook-using-macos/5928/6 "2022-09-08T06:29:04Z")
Right, I forgot about that.
I wonder if we could disable lfs in the vtkm submodule, VTK nor ParaView are not using the lfs data, is that correct ?
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [October 17, 2022, 9:20pm UTC](https://discourse.paraview.org/t/import-paraview-5-8-1-module-in-python-3-7-on-anaconda-juypter-notebook-using-macos/5928/7 "2022-10-17T21:20:49Z")
Enabling or disabling is a user-side thing; there’s nothing that we can put into our repository that will block this. `git-lfs` loves installing itself system- or user-wide so that it “just works” for any repo. Myself, I don’t do that and only enable `git-lfs` for specific projects where I need to interact with it using `git lfs install --local` in the relevant repositories (only needed once).