Thanks, I guess I just wanted to simply import "paraview.simple" as I usually do with other modules that I get from pip. Perhaps I should run paraview scripts "externally" by using pvpython.
On Fri, Mar 16, 2018 at 1:15 PM, Shawn Waldon <[email protected]> wrote: > On Fri, Mar 16, 2018 at 12:24 PM, Miguel Arriaga <[email protected]> > wrote: > >> Thanks Shawn, >> I was just wondering, would it be possible for the developers to change >> the location of the paraview module such that adding the location of the >> module to the python path would not import all other site-packages? Maybe >> I'm missing something, but it seems to me that this way we would be able to >> avoid these issues. >> >> > Forwarding to the list since I don't make these decisions. For what it is > worth, I feel like it increases the maintenance burden on the developers > too much for a niche use case. > > Please keep the mailing list in the CC. > > Shawn >
_______________________________________________ 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: https://public.kitware.com/mailman/listinfo/paraview
