[Paraview] Issue with Python path variable change from ver 5.2 onward

[Cory Quammen]

Evan,

I have filed a bug report [1]. I don't recall if this was an
intentional change, but it appears to be causing you and at least one
other person problems.

Thanks,
Cory

[1] https://gitlab.kitware.com/paraview/paraview/issues/17699

On Thu, May 25, 2017 at 12:33 AM, Evan Kao <tossin at gmail.com> wrote:
> Hello all,
>
> I've encountered a minor, but annoying issue (for me, at least) when using
> Python in Paraview (installed from binaries on Windows).  I noticed that
> since version 5.2, the Paraview-related paths are appended to the end of the
> system PYTHONPATH variable, instead of inserted at the beginning.  For
> instance:
>
>
> v5.1.2
>
>>>> import sys
>
>>>> for p in sys.path:
>
> ... print p
>
> ...
>
> D:\Program Files\ParaView 5.1.2\lib\paraview-5.1\site-packages\vtk
>
> D:\Program Files\ParaView 5.1.2\lib\paraview-5.1\site-packages <- Paraview
> VTK code
>
> D:\Program Files\ParaView 5.1.2\lib\paraview-5.1
>
> D:\Program Files\ParaView 5.1.2\bin
>
> ...
>
> D:\Anaconda2\Lib\site-packages <- original system PYTHONPATH paths
>
> etc...
>
> D:\Program Files\ParaView 5.1.2\bin\python27.zip
>
> D:\Program Files\ParaView 5.1.2\bin\DLLs
>
> D:\Program Files\ParaView 5.1.2\bin\lib
>
> D:\Program Files\ParaView 5.1.2\bin\lib\plat-win
>
> D:\Program Files\ParaView 5.1.2\bin\lib\lib-tk
>
> D:\Program Files\ParaView 5.1.2\bin
>
> D:\Program Files\ParaView 5.1.2\bin\lib\site-packages
>
>
>
> v5.4.0-RC2:
>
>>>> import sys
>
>>>> for p in sys.path:
>
> ... print p
>
> ...
>
> D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin
>
> ...
>
> D:\Anaconda2\Lib\site-packages <- original system PYTHONPATH paths
>
> etc...
>
> D:\Program Files\ParaView
> 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\python27.zip
>
> D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\DLLs
>
> D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib
>
> D:\Program Files\ParaView
> 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\plat-win
>
> D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\lib-tk
>
> D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin
>
> D:\Program Files\ParaView
> 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages <- Paraview VTK
> code
>
> D:\Program Files\ParaView
> 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\win32
>
> D:\Program Files\ParaView
> 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\win32\lib
>
>
>
> This is a problem for me because I like to use the Python Programmable
> Filter a lot, but now whenever I import VTK, it will first look for the
> version of VTK on my system, rather than the one used by Paraview, which
> leads to conflict errors.
>
> I know this can be fixed by running the Python Shell and manipulating the
> PYTHONPATH variable from there, but I'd have to do that every time I open
> Paraview, which is pretty cumbersome.  Is there a way to change this
> behavior?  Could it be a changed back in future versions or was there a
> reason for this change?
>
> Thanks,
> Evan Kao
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.