I think you've spotted an inconsistency. In setup.py we check for mayavi with "import mayavi", but we never actually make an import of mayavi in this way. The "import mayavi" in setup.py may be a vestige of older versions of mayavi, which worked that way. So, if both "import enthought" and "enthought import mayavi" then there is a good chance that mayavi will work with fipy despite what setup.py is reporting. Does it work if you run an example with mayavi set as the viewer?
On Tue, Nov 16, 2010 at 10:25 AM, Ram Balachandran <ram.balachand...@gmail.com> wrote: > "import enthought" and from "enthought import mayavi" works at the command > line. The commands run without producing errors. But would that make fipy > recognize mayavi when we run "python setup.py test" from the dos prompt? > > Ram. > > On Mon, Nov 15, 2010 at 3:05 PM, Daniel Wheeler <daniel.wheel...@gmail.com> > wrote: >> >> Can you do "import enthought" and "from enthought import mayavi" at >> the command line? >> >> On Mon, Nov 15, 2010 at 11:00 AM, Ram Balachandran >> <ram.balachand...@gmail.com> wrote: >> > Hello all, >> > >> > I installed EPD 6.3.1 on my windows 32-bit machine. I installed pysparse >> > and >> > fipy using the .exe files that I downloaded. When I test fipy using >> > 'python >> > setup.py test' from my fipy folder all my tests run OK. But I am getting >> > messages that say that mayavi, PyTrilinos, gist and mpi4py are not >> > installed. They also indicate that scipy, numpy and a few other modules >> > have >> > been installed. All the modules that fipy identifies are found in >> > C:\Python26\Lib\site-packages\. I know that EPD comes with mayavi and >> > can be >> > found in C:\Python26\Lib\site-packages\enthought\. How do I make fipy >> > recognize mayavi which is in a different folder? >> > >> > Thanks >> > Ram. >> > >> >> >> >> -- >> Daniel Wheeler >> > > -- Daniel Wheeler
