[Numpy-discussion] Py3k and numpy
Thu Dec 4 17:45:42 CST 2008
On Fri, Dec 5, 2008 at 4:03 AM, Robert Kern <email@example.com> wrote:
> On Thu, Dec 4, 2008 at 12:57, Charles R Harris
> <firstname.lastname@example.org> wrote:
>> On Thu, Dec 4, 2008 at 9:39 AM, Charles R Harris <email@example.com>
>>> On Thu, Dec 4, 2008 at 1:20 AM, Erik Tollerud <firstname.lastname@example.org>
>>>> I noticed that the Python 3000 final was released today... is there
>>>> any sense of how long it will take to get numpy working under 3k? I
>>>> would imagine it'll be a lot to adapt given the low-level change, but
>>>> is the work already in progress?
>>> I read that announcement too. My feeling is that we can only support one
>>> branch at a time, i.e., the python 2.x or python 3.x series. So the easiest
>>> path to 3.x looked to be waiting until python 2.6 was widely distributed,
>>> making it the required version, doing the needed updates to numpy, and then
>>> using the automatic conversion to python 3.x. I expect f2py, nose, and other
>>> tools will also need fixups. Guido suggests an approach like this for those
>>> needing to support both series and I really don't see an alternative unless
>>> someone wants to fork numpy ;)
>> Looks like python 2.6 just went into Fedora rawhide, so it should be in the
>> May Fedora 11 release. I expect Ubuntu and other leading edge Linux distros
>> to have it about the same time. This probably means numpy needs to be
>> running on python 2.6 by early Spring.
> It does. What problems are people seeing? Is it just the Windows build
> that causes people to say "numpy doesn't work with Python 2.6"?
Up to recently, numpy had some failures with python.org python 2.6 in
x86 - but those are fixed now. The windows issues are mostly sorted
out (and the missing information for reliable build has been
integrated in python 2.6.1 I believe
F2py does not work, though - which is the main issue to make scipy
work on 2.6, as far as I can see.
More information about the Numpy-discussion