View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0006456ParaView(No Category)public2008-02-27 15:032009-05-13 13:59
ReporterKen Moreland 
Assigned ToUtkarsh Ayachit 
PriorityhighSeverityfeatureReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version3.4Fixed in Version3.4 
Summary0006456: Set python path for programmable filter outside of scripts
DescriptionWe need the ability to set the python path for the programmable filter outside of the scripts themselves. There should be a text edit in the object inspector that gets pre-pended to the python path (except for .). The justification for this feature is that right now in order to set the path for the filter scripts, you have to put the path in the scripts themselves, and then the scripts get tied to a single server machine and can no longer be applied to other servers.
TagsNo tags attached.
Project
Topic Name
Type
Attached Files

 Relationships

  Notes
(0011044)
Berk Geveci (administrator)
2008-04-02 16:32

This can be accomplished by setting the PYTHONPATH. Why do we have to make the programmable filter more complicated?
(0012153)
Berk Geveci (administrator)
2008-05-29 13:41

We are going to add support for setting the python path to server options. This will be in the form of being able to set a list of environmental variable for the server in the xml file.
(0012503)
Utkarsh Ayachit (administrator)
2008-06-24 11:50

There a couple of ways of dealing with the environment variable server options.

1) Use ParaView's client side XMLs for server options i.e add some XML elements to
the server configuration xml defined here http://www.paraview.org/Wiki/Server_Configuration [^] to set the environment variables. However, in this case, it will work only when using ParaView client and not when connecting to the server using pvpython.

2) Use the paraview server options (as described here:
http://www.paraview.org/Wiki/ParaView:FAQ#How_do_I_specify_cave_parameters_in_ParaView_2.2_and_later.3F [^]
)

In this case, there already exists a "Environment" tag where the user can specify the environment variables, including PYTHONPATH.
This will work even for server connected to using pvpython or any other client.

Suggestions?
(0012526)
Greg Weirs (developer)
2008-06-25 17:32

Returning to the original feature request, what I would like is to be able to dynamically modify the the server-side python path(used by the programmable filter) from the client-side proxy to that filter.

There is an (as far as I can tell) undocumented mechanism to define and set arbitrary programmable filter properties from the client. These properties are accessible to the programmable filter script. Rather than hard-code the desired PYTHONPATH in the script (which is not dynamic) I can do it through this undocumented mechanism. However, I believe the server-side PYTHONPATH used by the programmable filter script is an important enough property that it should be promoted to a "full" (not arbitrary) property of the programmable filter.

The xml server configuration file is not dynamic, and applies to all users of the pvserver. I am looking for something that could point to directories of a particular user or restricted user group on the fly.
(0012649)
Utkarsh Ayachit (administrator)
2008-07-08 08:40

As per final request, adding a "PythonPath" property which can be set with a semi-colon separated list of directories to add to python search paths.

/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPythonProgrammableFilter.cxx,v <-- Servers/Filters/vtkPythonProgrammableFilter.cxx
new revision: 1.32; previous revision: 1.31
/cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPythonProgrammableFilter.h,v <-- Servers/Filters/vtkPythonProgrammableFilter.h
new revision: 1.13; previous revision: 1.12
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/Resources/pythonfilter.xml,v <-- Servers/ServerManager/Resources/pythonfilter.xml
new revision: 1.13; previous revision: 1.12
(0012681)
Alan Scott (manager)
2008-07-09 16:52

Closed. Greg - if this does not work, let me know and I will re-open it.

alan

 Issue History
Date Modified Username Field Change
2008-02-27 15:03 Ken Moreland New Issue
2008-03-18 19:00 Alan Scott Priority normal => high
2008-03-19 20:00 Berk Geveci Status backlog => tabled
2008-03-19 20:00 Berk Geveci Assigned To => Berk Geveci
2008-03-19 20:02 Berk Geveci Target Version => Python support
2008-04-02 16:32 Berk Geveci Note Added: 0011044
2008-04-02 16:32 Berk Geveci Status tabled => @20@
2008-05-01 13:27 Berk Geveci Status @20@ => tabled
2008-05-01 13:27 Berk Geveci Status tabled => @30@
2008-05-29 13:41 Berk Geveci Note Added: 0012153
2008-05-29 13:42 Berk Geveci Status @30@ => tabled
2008-05-29 13:42 Berk Geveci Assigned To Berk Geveci => Utkarsh Ayachit
2008-06-24 11:50 Utkarsh Ayachit Note Added: 0012503
2008-06-24 11:50 Utkarsh Ayachit Status tabled => @20@
2008-06-25 17:32 Greg Weirs Note Added: 0012526
2008-07-08 08:40 Utkarsh Ayachit Status @20@ => @80@
2008-07-08 08:40 Utkarsh Ayachit Resolution open => fixed
2008-07-08 08:40 Utkarsh Ayachit Note Added: 0012649
2008-07-09 16:52 Alan Scott Status @80@ => closed
2008-07-09 16:52 Alan Scott Note Added: 0012681
2009-05-13 13:58 Utkarsh Ayachit Target Version Python support => 3.4
2009-05-13 13:59 Utkarsh Ayachit Fixed in Version => 3.4
2011-06-16 13:10 Zack Galbreath Category => (No Category)


Copyright © 2000 - 2018 MantisBT Team