[Paraview] Python Error in Python Shell

[Mike Jackson]

Yep. Mine too. This came about from my work in packaging ParaView for  
OS X. I wasn't copying the .so files because my scripts didn't _know_  
about them. If they are just plugins then I can copy them to the  
proper location within the .app package. I was just looking at  
_where_ in the cmake files to hook in so that I can create the  
scripts that will copy and update the .so files.

Thanks
-- 
Mike Jackson   Senior Research Engineer
Innovative Management & Technology Services


On Feb 27, 2008, at 2:24 PM, Eric E. Monson wrote:

> Hey Mike,
>
> On my system both the libvtkCommonPython.so and  
> libvtkCommonPythonD.dylib both end up in the build/bin directory,  
> like any other plugin or library, in case that helps.
>
> -Eric
>
> ------------------------------------------------------
> Eric E Monson
> Duke Visualization Technology Group
>
>
>
> On Feb 27, 2008, at 2:11 PM, Mike Jackson wrote:
>
>> I found the "D" section of the Python cmake code and it seems to  
>> be hard coded in there. So you are probably correct, it doesn't  
>> stand for "Debug".
>>
>> I guess I need to track down where the libvtkCommonPython.so is  
>> created to see if I can tie into that cmake code to create shell  
>> scripts that will copy and update those as plugins. Any ideas  
>> where those targets are created?
>>
>> -- 
>> Mike Jackson   Senior Research Engineer
>> Innovative Management & Technology Services
>>
>>
>> On Feb 27, 2008, at 2:01 PM, Berk Geveci wrote:
>>
>>> The .so is the plugin module. It links against the .dylib which the
>>> plugin links against. You need both. I am not sure what the D stands
>>> for but it is not debug. Dynamic maybe.
>>>
>>> On 2/27/08, Mike Jackson <imikejackson at gmail.com> wrote:
>>>> I am working on a new packaging shell script for OS X and I am
>>>> getting the following error when I attempt to run the Python Shell:
>>>>
>>>>
>>>> Python 2.3.5 (#1, Jan 13 2006, 20:13:11)
>>>> [GCC 4.0.1 (Apple Computer, Inc. build 5250)] on darwin
>>>>>>>
>>>> Traceback (most recent call last):
>>>>   File "<string>", line 1, in ?
>>>>   File "/Users/Shared/Toolkits/ParaView3/bin/paraview.app/Contents/
>>>> SharedSupport/paraview/__init__.py", line 40, in ?
>>>>     from libvtkPVServerCommonPython import *
>>>> ImportError: No module named libvtkPVServerCommonPython
>>>>>>>
>>>>
>>>> Taking a look around I see that ParaView is linked against
>>>> libvtkPVServerCommonPythonD.dylib. There is also a
>>>> libvtkPVServerCommonPython.so library. Is that a plugin that I am
>>>> missing maybe?
>>>>
>>>> Also, not sure of the naming convention, but I did a Release build
>>>> but I still have libvtkPVServerManagerPythonD,
>>>> libvtkPVServerCommonPythonD, libvtkCommonPythonD as dylibs. I would
>>>> think those names would be missing the "D" at the end of the name.
>>>>
>>>> Any help or insights would be greatly appreciated.
>>>>
>>>> --
>>>> Mike Jackson
>>>> imikejackson & gmail * com
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> ParaView mailing list
>>>> ParaView at paraview.org
>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>>
>>
>> _______________________________________________
>> ParaView mailing list
>> ParaView at paraview.org
>> http://www.paraview.org/mailman/listinfo/paraview
>