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) I hope this work can be used to get a numpy 1.5.x branch started. 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
Hi Christoph, Sorry for the slow reply. This looks quite good! On Sat, Jun 26, 2010 at 3:31 AM, Christoph Gohlke <cgohlke@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
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
participants (3)
-
Christoph Gohlke -
Pauli Virtanen -
Ralf Gommers