Good Morning,
A colleague, who has just received his new windows 7 64 bits computer also
tried to get Paraview 3.12 64 bits, and to make scipy.signal avalaible.
He encountered the same issue as me, and can't import scipy.signal in the
paraview python shell.
Should I then put a bug in Mantis Bug
Yes please, and detailed steps you're taking to produce the issue. Thanks!
2011/12/5 Aurélien Marsan aur.mar...@gmail.com
Good Morning,
A colleague, who has just received his new windows 7 64 bits computer also
tried to get Paraview 3.12 64 bits, and to make scipy.signal avalaible.
He
Ok that is here
http://public.kitware.com/Bug/view.php?id=12607
Hope this is detailled enough. If not, please let me know in order I add
the missing informations.
Good afternoon.
Le 5 décembre 2011 14:51, David Partyka david.part...@kitware.com a écrit
:
Yes please, and detailed steps you're
Some news about always the same issue.
I compile Paraview 3.12 by my own, using the Python 2.7 installed on my
system.
Again, I can not import scipy.signal.
Does someone achieve this ?
Thanks,
A.Marsan
Le 18 novembre 2011 15:14, Aurélien Marsan aur.mar...@gmail.com a écrit :
Non there isn't
Sharing my experience :
I tried to do the same with the Paraview 3.12 32 bits binary release --
same issue.
So I came back to the 3.10.1 32bits release, that I know it worked on
windows XP. It works again on windows 7.
Yet, all my tools, that require the import of scipy.signal among others,
are
Is there any output on the python shell like failing to load a module?
2011/11/16 Aurélien Marsan aur.mar...@gmail.com
One more time, I'm in trouble.. !
When importing scipy.signal in the python shell, within paraview 3.12.0 64
bits, it becomes locked... and I do have to kill the process.
One more time, I'm in trouble.. !
When importing scipy.signal in the python shell, within paraview 3.12.0 64
bits, it becomes locked... and I do have to kill the process.
Though, when executing pvpython, I can import scipy.signal without any
trouble, and it seems to work well.
So what do I miss