<div>Hi Richard,</div><div><br></div>The final release of ParaView 3.12 will include numpy, cython, h5py and matplotlib just so you're aware.<br><br><div class="gmail_quote">On Fri, Oct 7, 2011 at 3:32 PM, Richard Strelitz <span dir="ltr"><<a href="mailto:strelitz@lanl.gov">strelitz@lanl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal">I have been asked to develop a suite of seismic exploration tools based on ParaView to geophysicists who are not computer savvy. For the foreseeable future, they will run these apps on workstations and laptops. They do not have nor do they intend to build ParaView, install C++ compilers, or do anything more than run the app on their data. I would like to use Python to develop the app-specific codes (readers, filters, renderers, etc.) many of which use matplotlib and other modules not provided in the pvpython site-packages path. I can install environments like those in pythonxy (my preferred vehicle) or in any number of other similar packages. Are the packages in the current PV distribution unchanged from what one can download from the standard repositories (like PiPy, etc.)? How do I avoid duplication of modules or worse, possible conflict?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Any advice or experience would be appreciated.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><font color="#888888"><p class="MsoNormal">Richard<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p></font></div></div><br>_______________________________________________<br>
Paraview-developers mailing list<br>
<a href="mailto:Paraview-developers@paraview.org">Paraview-developers@paraview.org</a><br>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
<br></blockquote></div><br>