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?
___
On Thu, Dec 4, 2008 at 1:20 AM, Erik Tollerud [EMAIL PROTECTED]wrote:
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
On Thu, Dec 4, 2008 at 9:39 AM, Charles R Harris
[EMAIL PROTECTED]wrote:
On Thu, Dec 4, 2008 at 1:20 AM, Erik Tollerud [EMAIL PROTECTED]wrote:
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
On Thu, Dec 4, 2008 at 12:57, Charles R Harris
[EMAIL PROTECTED] wrote:
On Thu, Dec 4, 2008 at 9:39 AM, Charles R Harris [EMAIL PROTECTED]
wrote:
On Thu, Dec 4, 2008 at 1:20 AM, Erik Tollerud [EMAIL PROTECTED]
wrote:
I noticed that the Python 3000 final was released today... is there
On Dec 4, 2008, at 2:03 PM, Robert Kern wrote:
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?
There is currently no official Mac OSX binary for numpy for python 2.6,
but you can build it from source. Is there
On Thu, Dec 4, 2008 at 12:15 PM, Tommy Grav [EMAIL PROTECTED] wrote:
On Dec 4, 2008, at 2:03 PM, Robert Kern wrote:
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?
There is currently no official Mac OSX
From my experience working on my own projects and Cython:
* the C code making Python C-API calls could be made to
version-agnostic by using preprocessor macros, and even some
compatibility header conditionally included. Perhaps the later would
be the easiest for C-API calls (we have a lot already
