[Paraview] Dose pvpython work with python 3.x ?

Marcus D. Hanwell marcus.hanwell at kitware.com
Wed Nov 23 15:22:23 EST 2016


On Mon, Nov 21, 2016 at 2:21 PM, Marcus D. Hanwell
<marcus.hanwell at kitware.com> wrote:
>
> On Mon, Nov 21, 2016 at 1:24 PM, Cory Quammen <cory.quammen at kitware.com> wrote:
> >
> > I'm not sure what the problem is. We've barely tested building against Python 3, and I personally have never built with Python 3, so it's quite possible you have uncovered a problem. Unfortunately, I don't have time to investigate further at the moment.
> >
> > If you figure it out, please let us know.
> >
> Just to add one small data point, I was able to compile ParaView
> master against Python 3 on my Linux system. Right now it looks like
> opening the Python shell causes a segfault (at least for me). Tomviz
> is a ParaView based GUI, and it also hits a compile failure at the
> moment.
>
> Hopefully we will have more time to look at this in December/January,
> but it is not a high priority right now (although I don't want to wait
> too long).

I just realized that my test was a little unfair, I used the build
parameters for ParaView that Tomviz uses to enable threaded Python
support,

     VTK_PYTHON_FULL_THREADSAFE:BOOL=ON
     VTK_NO_PYTHON_THREADS:BOOL=OFF

If I switch that to

     VTK_NO_PYTHON_THREADS:BOOL=ON

then ParaView seems to work quite well, and I can start the Python
shell without issue. This is obviously a concern for us as we would
like to use threaded Python to execute workloads on a worker thread
that doesn't freeze the user interface, but if you leave these CMake
flags at their default it would appear to be a usable ParaView build
in my limited testing.


More information about the ParaView mailing list