[Numpy-discussion] numpy.fromiter hiding exceptions

the original exception, and get the stacktrace in ipython (or wherever I am working). Is this possible in some easy way, or am I stuck with the equivalent of if debug: mygenerator = list(mygenerator) a = np.fromiter(iter(mygenerator), dtype=xxx, count=xxx) -- Åsmund Hjulstad, asm

[Numpy-discussion] F2py and Absoft Fortran compiler v11.0 (unable to locate U77.lib) [patch]

','f77math','U77']) BTW, the performance increase compared to gfortran v4.5.0 is really noticeable, perhaps more than 50%. Best regards, Åsmund Hjulstad ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy

Re: [Numpy-discussion] PyGTK breaks fortran extension???

2010/9/3 Pauli Virtanen p...@iki.fi Fri, 03 Sep 2010 08:53:00 +0300, Åsmund Hjulstad wrote: I have a f2py wrapped fortran extension, compiled using gcc-mingw32 (v.4.5.0), numpy 1.5, Python 2.7, where I am experiencing the strangest behaviour. It appears that loading pygtk breaks my fortran

[Numpy-discussion] PyGTK breaks fortran extension???

this with mingw. Best regards, Åsmund Hjulstad, asm...@hjulstad.com ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Evaluating performance of f2py extensions with gprof, why spending time _gfortran_compare_string

2010/8/18 Åsmund Hjulstad asmund.hjuls...@gmail.com I am calling a few functions in a fortran library. All parameters are short (longest array of 20 elements), and I do three calls to the fortran library pr iteration. According to the python profiler (running the script as %run -p in ipython

[Numpy-discussion] Evaluating performance of f2py extensions with gprof, why spending time _gfortran_compare_string

. -- Åsmund Hjulstad, asm...@hjulstad.com ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] Building f2py extensions on AMD64 with Python 2.7 Numpy 1.5, MSVC 2008 Pro and gfortran

it working. GFortran is from MinGW-w64 project on sourceforge, version 4.5.1 prerelease. Any pointers or other experiences? Regards, Åsmund Hjulstad ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy

Re: [Numpy-discussion] Building f2py extensions on AMD64 with Python 2.7 Numpy 1.5, MSVC 2008 Pro and gfortran

2010/8/16 Sturla Molden stu...@molden.no Two criticial import libraries for mingw-w64 are missing (libpython26.a and msvcr90.a). We cannot build C extensions for Python with mingw-w64. If you can build with disutils, your are not using mingw-w64 but another C compiler. You are correct. The