On Sat, Dec 26, 2009 at 4:15 PM, Charles R Harris <charlesr.har...@gmail.com > wrote:
> > > On Sat, Dec 26, 2009 at 2:19 PM, Gökhan Sever <gokhanse...@gmail.com>wrote: > >> >> >> On Thu, Dec 24, 2009 at 4:57 PM, David Cournapeau <courn...@gmail.com>wrote: >> >>> On Wed, Dec 23, 2009 at 1:41 AM, Gökhan Sever <gokhanse...@gmail.com> >>> wrote: >>> > >>> > >>> > On Tue, Dec 22, 2009 at 9:05 AM, David Cournapeau <courn...@gmail.com> >>> > wrote: >>> >> >>> >> Hi, >>> >> >>> >> I have just released the 2nd release candidate for numpy 1.4.0, which >>> >> fixes a few critical bugs founds since the RC1. Tarballs and binary >>> >> installers for numpy/scipy may be found on >>> >> https://sourceforge.net/projects/numpy. >>> >> >>> >> cheers, >>> >> >>> >> David >>> >> _______________________________________________ >>> >> NumPy-Discussion mailing list >>> >> NumPy-Discussion@scipy.org >>> >> http://mail.scipy.org/mailman/listinfo/numpy-discussion >>> > >>> > This release results with the same import error on my system that I >>> posted >>> > on >>> >>> Don't use develop, and install numpy normally, but from scratch. >>> Develop mode has some quircks, and it does not worth it unless you >>> want to work on numpy code yourself IMHO, >>> >> >> OK, a clean svn check-out and python setup.py install I get another >> interesting import error: >> >> [gse...@ccn ~]$ pwd >> /home/gsever >> [gse...@ccn ~]$ python >> >> Python 2.6 (r26:66714, Jun 8 2009, 16:07:26) >> [GCC 4.4.0 20090506 (Red Hat 4.4.0-4)] on linux2 >> Type "help", "copyright", "credits" or "license" for more information. >> >>> import numpy >> Traceback (most recent call last): >> File "<stdin>", line 1, in <module> >> File "/home/gsever/Desktop/python-repo/numpy/numpy/__init__.py", line >> 123, in <module> >> raise ImportError(msg) >> ImportError: Error importing numpy: you should not try to import numpy >> from >> its source directory; please exit the numpy source tree, and >> relaunch >> your python intepreter from there. >> >>> >> >> I launch the interpreter from a different directory than where the sources >> located, however it still complains. >> >> For the develop, it is one of easiest ways to catch up the bug-fixes even >> though I don't work on the source directly. So far besides a few glitches it >> was always working. I also install scipy, ipython, matplotlib, sympy and all >> other available packages using develop. Keep the checkouts in the directory >> on my desktop and if/when necessary do svn up or whichever command it >> corresponds to their respective vcs. I wonder how other people keep up the >> changes easily without using develop option. >> >> > I never see any of these problems and apparently no one else does either. > There is something unique about your system. What does os.getcwd() return? > > Chuck > > I removed numpy.egg-link (a remnant from setupegg.py develop) file under /usr/lib/python2.6/site-packages. Still I get the same error. Your query returns the same as pwd command: >>> import os >>> os.getcwd() '/home/gsever/Desktop' >>> exit() [gse...@ccn Desktop]$ pwd /home/gsever/Desktop > > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion > > -- Gökhan
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
