gmane.comp.python.fipy

Zhiwen Liang | 16 Jul 22:37

Re: Problems on Installing New Fipy

Hi,

On Wed, Jul 16, 2008 at 3:28 PM, Jonathan Guyer <guyer-R3+/ord2DXQ@public.gmane.org> wrote:

On Jul 16, 2008, at 3:14 PM, Zhiwen Liang wrote:

Thank you very much for providing the information. I used the patch and now I can install fipy. I think except for the bug in setuptools, my biggest problem was I tried to install fipy in a directory that setuptools does not like. Please see:

http://peak.telecommunity.com/DevCenter/EasyInstall#mac-os-x-user-installation

However, if I install fipy in ~/Library/Python/2.3/site-packages/, as required, I have problem with my other modules.

What problems? What other modules?

I tried the diffusion example but got the following error:

Traceback (most recent call last):

File "<stdin>", line 1, in ?

File "/Users/liangz/Library/Python/2.3/site-packages/fipy/viewers/__init__.py", line 112, in make

raise ImportError, "Failed to import a viewer: %s" % str(errors)

ImportError: Failed to import a viewer: ['gistViewer: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()', 'gnuplotViewer: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()', "matplotlibViewer: 'module' object has no attribute 'ion'", 'mayaviViewer: Mayavi does not display useful 1D data', "multiViewer: 'module' object has no attribute 'make'", "tsvViewer: 'module' object has no attribute 'make'"]

This error will appear whenever I tried "viewers.make". This might not be relevant to the installation problem but it never happened to me before.

I really hope that I can install fipy in the place I want.

Which is where?

It would be more convenient to use "stow" to have different versions of the same application and then "stow" the version you like. This will require installing things in a stow directory.

For the record, we never install FiPy at all. We simply adjust our $PYTHONPATH to point to whichever copy we want to use. Installing is fine, and can simplify a few things, but it's not necessary.

Depending on exactly what you are trying to do, you might want to look into http://pypi.python.org/pypi/virtualenv

(I have not had good luck with virtual-python.py)

So I wonder if there is a setup.py that does not use setuptools but still can install the new fipy?

No, we will not be supporting two different setup.py systems. We certainly are interested, however, in correcting any problems.

Thanks again,

Zhiwen