# Current status of PVGeo and Paraview
**URL:** https://discourse.paraview.org/t/current-status-of-pvgeo-and-paraview/3804
**Category:** ParaView Support
**Created:** [March 12, 2020, 7:37pm UTC](https://discourse.paraview.org/t/current-status-of-pvgeo-and-paraview/3804 "2020-03-12T19:37:40Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@jwesolow](https://discourse.paraview.org/u/jwesolow)
#### Post date: [March 12, 2020, 7:37pm UTC](https://discourse.paraview.org/t/current-status-of-pvgeo-and-paraview/3804/1 "2020-03-12T19:37:40Z")
Hi,
I’m not sure if I should be asking this here or not, so please let me know if I should take the question to PVGeo. This is unrelated to the other issue I just posted.
Since Paraview has converted to Python 3, the old instructions for using PVGeo with Paraview seem deprecated. I tried setting up a similar Anaconda environment with Python 3.7.4 but it did not work, possibly because I had trouble getting VTK to install (even though it is available for 3.7 on Windows) in the environment. According to the instructions, the 2.7 version of PVGeo used the PVPython built-in VTK but I’m not sure the 3.7 version does.
I have searched for updated information but cannot really find anything other than the instructions for Paraview 5.6.0 with Python 2.7. Is there any current information available?
Thanks!
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 13, 2020, 2:29am UTC](https://discourse.paraview.org/t/current-status-of-pvgeo-and-paraview/3804/2 "2020-03-13T02:29:57Z")
The old PVGeo is not working with new version of ParaView.
They have been taken over in another project from @banesullivan :
> **[OpenGeoVis/PVGeo](https://github.com/OpenGeoVis/PVGeo)**
>
> Python package of VTK-based algorithms to analyze geoscientific data and models - OpenGeoVis/PVGeo
Please note, none of these tools have ever been officially supported by ParaView or Kitware.
---
### Author:  [@jwesolow](https://discourse.paraview.org/u/jwesolow)
#### Post date: [March 13, 2020, 2:59am UTC](https://discourse.paraview.org/t/current-status-of-pvgeo-and-paraview/3804/3 "2020-03-13T02:59:46Z")
Thank you. I will take any further questions to them.
---
### Author:  [@banesullivan](https://discourse.paraview.org/u/banesullivan)
#### Post date: [April 22, 2020, 12:02pm UTC](https://discourse.paraview.org/t/current-status-of-pvgeo-and-paraview/3804/4 "2020-04-22T12:02:26Z")
Hi there, I am aware of the current compatibility issues between PVGeo and the latest ParaView. Unfortunately, my bandwidth is stretched thin and I haven’t had time to update PVGeo as my open-source contributions have been focused on PyVista. Also, I have been waiting for Python 3 to be shipped with ParaView on all OS (Mac is still 2.7).
It would greatly help if you could open an issue about your challenges in the [PVGeo GitHub repository](https://github.com/OpenGeoVis/PVGeo)
I will try to take a look at it this week in my free time and see if I can get PVGeo up and running with the distributed version of ParaView as well as the version now [coming from Conda-forge](https://anaconda.org/conda-forge/paraview)
* * *
And I want to emphasize @mwestphal’s note: PVGeo is a third party plugin suite maintained by myself and not Kitware