[Paraview] Determining the paraview-version from a Python-script

[pat marion]

Hi Bernhard,

The c++ class, vtkSMProxyManager, gets wrapped by a python class.  So
dir(pxm) only shows you the methods added by the python class.  To see
the available c++ methods, try dir(pxm.SMProxyManager)  The proxy
manager is a special case, most pvpython objects are instances of
Proxy and you can do dir(foo.SMProxy) to see the c++ documentation.

The proxy manager c++ documentation is here:
http://www.paraview.org/ParaView3/Doc/Nightly/html/classvtkSMProxyManager.html

Also, if you browse the doxygen documentation
(http://www.paraview.org/ParaView3/Doc/Nightly/html/classes.html) keep
in mind that not all c++ methods are going to be available from
python.

Pat

On Mon, Aug 31, 2009 at 9:26 AM, Bernhard
Gschaider<bgschaid_lists at ice-sf.at> wrote:
>>>>>> On Mon, 31 Aug 2009 08:50:19 -0400
>>>>>> "UA" == Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
>
>    UA> To obtain the version number, you can do something as follows:
>    >>>> from paraview.simple import * pxm =
>    >>>> servermanager.ProxyManager() pxm.GetVersionMajor()
>    >>>> pxm.GetVersionMinor() pxm.GetVersionPatch()
>
>    UA> Utkarsh
>
> Thanks. That was exactly what I was looking for. (and it works in 3.4,
> too if I import the servermanager directly :) )
>
> Only question: how could I have found it on my own as the usual
> methods for introspection (dir(pxm), help(pxm))don't reveal these
> three methods?
>
> Bernhard
>
>    UA> On Mon, Aug 31, 2009 at 8:14 AM, Bernhard
>    UA> Gschaider<bgschaid_lists at ice-sf.at> wrote:
>    >> Thanks for the answer.
>    >>
>    >>>>>>> On Mon, 31 Aug 2009 12:50:35 +0200
>    >>>>>>> "JMF" == Jean M Favre <jfavre at cscs.ch> wrote:
>    >>
>    >>    JMF> Bernhard Gschaider wrote:
>    >>    >> Hi!     >>    >> I have a script that I want to keep
>    >> compatible with 3.4 and 3.6    >> (or at least it should fail
>    >> with a meaningful error message on    >> 3.4).
>    >>
>    >>    JMF> The following values are defined in 3.6 and above
>    >>
>    >>    JMF> paraview.compatibility.major
>    >> paraview.compatibility.minor
>    >>
>    >> I noticed those. But they are only defined in the "Python
>    >> Shell" from the GUI (to "3" and "5"). When I do
>    >>
>    >>>>> from paraview import compatibility print
>    >>>>> compatibility.minor,compatibility.major
>    >> in pvpython I get the answer
>    >>
>    >> None None
>    >>
>    >> which isn't too helpful ;)
>    >>
>    >> Bernhard
>    >>
>    >> _______________________________________________ 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
>    >>
>    >> Follow this link to subscribe/unsubscribe:
>    >> http://www.paraview.org/mailman/listinfo/paraview
>    >>
>    >>
>
>
> --
> ---------------------------------------------------------------------------
> DI Bernhard F.W. Gschaider
> ---------------------------------------------------------------------------
> EMail:  Bernhard.Gschaider at ice-sf.at
> WWW  : www.ice-sf.at
> Jabber : bgschaid at jabber.org
> Tel:    +43(3842)98282-42       Fax:    +43(3842)98282-02
> ---------------------------------------------------------------------------
>
> _______________________________________________
> 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
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>