Hi Ben, Those modules are needed and should be shipped with ParaView.
I believe the issue might be in the ParaView project itself not in its superbuild. I'm guessing, I messed up a dependency when I split the python code between python 2+3 and python 2 only. The python 2 one should depend on those libraries but not the python 2+3 code. Let me know how I can help to fix that, Thanks, Seb On Tue, Mar 14, 2017 at 9:39 AM, Ben Boeckel <ben.boec...@kitware.com> wrote: > On Tue, Mar 14, 2017 at 12:01:32 -0300, Rodnei Couto wrote: > > Python modules are different from 5.2 to 5.3 > > > > For example, inside* lib/python2.7/site-packages, *the version 5.2 has > the > > modules *autobahn, zope and twisted*, and the version 5.3 does not. > > > > I tried to copy the twisted and zope modules from version 5.2 to version > > 5.3, but a got others errors. > > > > By now, I reverted to release 5.2 in production environment. > > Looking at the superbuild, it appears that when ParaViewWeb got moved > from ParaView into its own repository, the flags that turned on pvweb > got removed and now there's nothing enabling those modules in ParaView's > build anymore. Do those packages need to be shipped with ParaView at all > now? If so, we'll need to add them to the superbuild specifically. If > not, some flag will need to be used to turn them on. > > --Ben >
_______________________________________________ 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: http://public.kitware.com/mailman/listinfo/paraview
