As a fellow Windows user I think I recognize what is going on. I encountered the same thing when trying to set up FiPy 2.1. I got my Windows setup to work by using the basic Python 2.5 (instead of enthought or PythonXY) and installing the python2.5 binaries for: Numpy 1.4.1 Scipy 0.7.2 Pysparse 1.1 FiPy 2.1 in that order.
Good luck. On Tue, May 18, 2010 at 10:47 AM, Daniel Wheeler <[email protected]> wrote: > > Hi Arvind, I am sorry to say that pysparse is having issues on Windows > with python 2.6. You can check this by doing "from pysparse import > precon" at the command line. It should give the same error. currently, > I have been unable to do a pysparse build that I can successfully > import using python 2.6 (pythonxy). Someone else put the binary on > sourceforge and I'm not sure what package of python 2.6 (pythonxy, > ehnthought ot just standard python) they used to build with, but it > doesn't work for me either. It could be an issue with pythonxy, so my > next attempt may be to try building pysparse using enthought. > Unfortunately, fipy is useless without pysparse. Sorry for the bad > news. > > On Tue, May 18, 2010 at 6:54 AM, Arvind Ajoy <[email protected]> wrote: >> >> Hi >> >> I am trying to install Fipy-2.1 on a Windows XP system. Following the >> manual, I have >> installed Python(x,y)-2.6.5.1, pysparse-1.1_rc1.win32-py2.6, and >> gmsh-2.4.2. No errors >> are reported when I run the installer for Fipy-2.1 . >> >> However, from the base FiPy directory, when I do the following with >> ipyhton, I get the following ... >> >> In [1]: run setup.py test >> running test >> running egg_info >> writing FiPy.egg-info\PKG-INFO >> writing top-level names to FiPy.egg-info\top_level.txt >> writing dependency_links to FiPy.egg-info\dependency_links.txt >> writing entry points to FiPy.egg-info\entry_points.txt >> reading manifest file 'FiPy.egg-info\SOURCES.txt' >> writing manifest file 'FiPy.egg-info\SOURCES.txt' >> running build_ext >> >> Python then crashes with the following message "python.exe has >> encountered a problem and >> needs to close. We are sorry for the inconvenience." >> >> Additionally, the same error occurs when i try >> >> In [1]: from fipy import * >> >> I have looked through the archives, but did not find any solutions to >> this error. >> >> I would appreciate any help! >> >> Regards >> >> Arvind Ajoy >> PhD Student, Electrical Engineering >> Indian Institute of Technology Madras >> >> >> >> >> >> >> >> >> >> >> python.exe has encountered a problem and needs to close. We are sorry >> for the inconvenience. >> >> > > > > -- > Daniel Wheeler > > >
