[Paraview] 4.0.1 release: problems loading paraview.simple in pvpython or pvbatch

[Utkarsh Ayachit]

Good to know. That's for reporting and testing the fix. 

Utkarsh 

On Jul 1, 2013, at 6:21 PM, Anthony Ruiz <ruizanthony at gmail.com> wrote:

> Thanks for the patch, it worked on my unix build. The nightly build
> for mac os x also works!
> 
> On Mon, Jul 1, 2013 at 1:50 PM, Anthony Ruiz <ruizanthony at gmail.com> wrote:
>> Thanks! I'll try the nightly binaries then.
>> 
>> On Thu, Jun 27, 2013 at 7:55 AM, Utkarsh Ayachit
>> <utkarsh.ayachit at kitware.com> wrote:
>>> Thanks for reporting. This issue has now been fixed. Attached is a
>>> patch. Once the bug moves into "Customer Review" state, feel free to
>>> try the nightly binaries. I'm attaching a patch too.
>>> 
>>> On Wed, Jun 26, 2013 at 1:27 PM, Anthony Ruiz <ruizanthony at gmail.com> wrote:
>>>> Thanks. This problem is not only on Mac OS X, I have the same problem
>>>> on a unix machine.
>>>> 
>>>> Anthony
>>>> 
>>>> On Wed, Jun 26, 2013 at 7:29 AM, Utkarsh Ayachit
>>>> <utkarsh.ayachit at kitware.com> wrote:
>>>>> Thanks for reporting this. I've reported a bug:
>>>>> http://paraview.org/Bug/view.php?id=14148
>>>>> Definitely sounds like a regression.
>>>>> 
>>>>> Utkarsh
>>>>> 
>>>>> On Tue, Jun 25, 2013 at 7:46 PM, Anthony Ruiz <ruizanthony at gmail.com> wrote:
>>>>>> Hi,
>>>>>> 
>>>>>> I'm having trouble while trying to import * in paraview.simple in
>>>>>> pvpython or pvbatch, using both the mac compiled version and a code
>>>>>> built from source on a unix machine, using the 4.0.1 release.
>>>>>> 
>>>>>> Once I added build/lib/site-packages to PYTHONPATH (this step was not
>>>>>> required in pvbatch 3.14.1), here's the error I get:
>>>>>> 
>>>>>>  File "~/local/build/lib/site-packages/paraview/vtk/__init__.py",
>>>>>> line 7, in <module>
>>>>>>    from vtkCommonCorePython import *
>>>>>> ImportError: No module named vtkCommonCorePython
>>>>>> 
>>>>>> If I launch pvbatch from a working directory and let the shell find
>>>>>> the executable in the path, I have the problem above. If I explicitly
>>>>>> launch the executable using its absolute path, I don't have that
>>>>>> problem (both were working in version 3.14.1). Is it an expected
>>>>>> change of behavior?
>>>>>> 
>>>>>> Thanks,
>>>>>> Anthony
>>>>>> _______________________________________________
>>>>>> 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