[Numpy-discussion] Py3k and numpy

Lisandro Dalcin dalcinl@gmail....
Thu Dec 4 20:31:37 CST 2008


>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 distilled in
Cython sources). Preprocessor conditionals would still be needed when
filling structs.

* Regarding Python code, I believe the only sane way to go is to make
the 2to3 tool to convert all the 2.x to 3.x code right.

* The all-new buffer interface as implemented in core Py3.0 needs
carefull review and fixes.

* The now-all-strings-are-unicode is going to make some headaches ;-)

* No idea how to deal with the now-all-integers-are-python-longs.



On Thu, Dec 4, 2008 at 5:20 AM, Erik Tollerud <erik.tollerud@gmail.com> 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 already in progress?
> _______________________________________________
> Numpy-discussion mailing list
> Numpy-discussion@scipy.org
> http://projects.scipy.org/mailman/listinfo/numpy-discussion
>



-- 
Lisandro Dalcín
---------------
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594


More information about the Numpy-discussion mailing list