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 really hope that I can install fipy in the place I want.
Which is where?
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.
