Re: [Numpy-discussion] OT: request help building pymex win64
On Fri, Jul 2, 2010 at 6:10 PM, David Cournapeau courn...@gmail.com wrote: Also, I would double check the issue is not something else altogether, Hi, I got it working eventually - it was something else altogether! I had made some mistakes in the changes I had made to get it to compile with visual studio that were causing the segfaults. Makes me think of the old phrase - problem is between keyboard and chair. Cheers Robin ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ? FAIL: test_print.test_complex_types(type 'numpy.complex64', )
On Wed, Jun 30, 2010 at 1:08 PM, Vincent Davis vinc...@vincentdavis.netwrote: I didn't find these documented anywhere, I have numpy(couple day old snapshot) install on python 2.7 OSX 64bit. I see those too. Can you open a ticket? Cheers, Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ? FAIL: test_print.test_complex_types(type 'numpy.complex64', )
On Sat, Jul 3, 2010 at 6:36 AM, Ralf Gommers ralf.gomm...@googlemail.com wrote: On Wed, Jun 30, 2010 at 1:08 PM, Vincent Davis vinc...@vincentdavis.net wrote: I didn't find these documented anywhere, I have numpy(couple day old snapshot) install on python 2.7 OSX 64bit. I see those too. Can you open a ticket? Open Ticket Ticket #1534 http://projects.scipy.org/numpy/ticket/1534 Vincent Cheers, Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Numpy 1.5 for Python 2.7 and 3.1
Hi Christoph, Sorry for the slow reply. This looks quite good! On Sat, Jun 26, 2010 at 3:31 AM, Christoph Gohlke cgoh...@uci.edu wrote: Dear NumPy developers, at http://projects.scipy.org/numpy/ticket/1520 I have posted a patch against numpy svn trunk r8464 that: 1) removes the datetime functionality 2) restores ABI compatibility with numpy 1.4.1 3) enables numpy to build and run on Python 2.7 and 3.1 (at least on Windows) Tested on OS X, there with python 2.6 and 2.7 all is well. With 3.1 it compiles fine but doesn't import, not sure why (I'm of course not actually in the source tree with the interpreter): Python 3.1.2 (r312:79360M, Mar 24 2010, 01:33:18) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type help, copyright, credits or license for more information. import numpy Traceback (most recent call last): File /Users/rgommers/Code/numpy/numpy/__init__.py, line 122, in module from numpy.__config__ import show as show_config ImportError: No module named __config__ During handling of the above exception, another exception occurred: Traceback (most recent call last): File stdin, line 1, in module File /Users/rgommers/Code/numpy/numpy/__init__.py, line 127, 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 hope this work can be used to get a numpy 1.5.x branch started. I hope so too. Probably someone familiar with the datetime changes should confirm that no trace of it is left. Cheers, Ralf Regarding Python 2.7, which is scheduled to be released within 2 weeks: numpy 1.4.1 does build and work with minor changes (http://projects.scipy.org/numpy/changeset/7926 and followups). However, for Python 2.7, the proposed patch will not be binary compatible with numpy 1.4.1 because it uses PyCapsule instead of PyCObject. Best, Christoph ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Numpy 1.5 for Python 2.7 and 3.1
Fri, 25 Jun 2010 12:31:36 -0700, Christoph Gohlke wrote: at http://projects.scipy.org/numpy/ticket/1520 I have posted a patch against numpy svn trunk r8464 that: 1) removes the datetime functionality 2) restores ABI compatibility with numpy 1.4.1 3) enables numpy to build and run on Python 2.7 and 3.1 (at least on Windows) [clip] This should make it easier to keep track of it: http://github.com/pv/numpy-work/tree/1.5.x I note that the patch contains some additional 3K porting. We/I'll need to split the patch into two parts: - Py3K or other miscellaneous fixes that should also go to the trunk - removing datetime and restoring the ABI I can probably take a look on this during EuroScipy. I'd also like to manually check the diff to svn/1.4.x So far, I think the following changes look like they should also go to the trunk: - numpy/numarray/_capi.c - numpy/lib/tests/test_io.py - numpy/core/include/numpy/npy_math.h -- Pauli Virtanen ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] PATCH: reference leaks for 'numpy.core._internal' module object
Sat, 03 Jul 2010 01:11:20 -0300, Lisandro Dalcin wrote: The simple test below show the issue. [clip: patch] Thanks, applied in r8469. [clip] PS: I think that such implementation should at least handle the very simple one/two character format (eg, 'i', 'f', 'd', 'Zf', 'Zd', etc.) without calling Python code... Of course, complaints without patches should not be taken too seriously ;-) We'll optimize once someone complains this makes their code slow ;) -- Pauli Virtanen ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] debian benchmarks
I was just looking at Debian's benchmark. LuaJIT is now (on median) beating Intel Fortran! Consider that Lua is a dynamic language very similar to Python. I know it's just a benchmark but this has to count as insanely impressive. Beating Intel Fortran with a dynamic scripting language... How is that even possible? If this keeps up we'll need a Python to Lua compiler very soon. And LuaJIT 2 is rumoured to be much faster than the current... Looking at median runtimes, here is what I got: gcc 1.10 LuaJIT1.96 Java 6 -server2.13 Intel Fortran 2.18 OCaml 3.41 SBCL 3.66 JavaScript V8 7.57 PyPy 31.5 CPython 64.6 Perl 67.2 Ruby 1.9 71.1 This means that LuaJIT can do in less than a day what CPython can do in a month. The only comfort for CPython is that Ruby and Perl did even worse. I wonder how much better CPython would do with NumPy on this benchmark? Sturla ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
