[Numpy-discussion] Status of NumPy and Python 3.3

[Ondřej Čertík]

On Fri, Jul 27, 2012 at 6:47 AM, Ralf Gommers
<ralf.gommers at googlemail.com> wrote:
>
>
> On Fri, Jul 27, 2012 at 10:43 AM, David Cournapeau <cournape at gmail.com>
> wrote:
>>
>> On Fri, Jul 27, 2012 at 9:28 AM, David Cournapeau <cournape at gmail.com>
>> wrote:
>> > On Fri, Jul 27, 2012 at 7:30 AM, Travis Oliphant <travis at continuum.io>
>> > wrote:
>> >> Hey all,
>> >>
>> >> I'm wondering who has tried to make NumPy work with Python 3.3.   The
>> >> Unicode handling was significantly improved in Python 3.3 and the
>> >> array-scalar code (which assumed a certain structure for UnicodeObjects) is
>> >> not working now.
>> >>
>> >> It would be nice to get 1.7.0 working with Python 3.3 if possible
>> >> before the release.     Anyone interested in tackling that little challenge?
>> >> If someone has already tried it would be nice to hear your experience.
>> >
>> > Given that we're late with 1.7, I would suggest passing this to the
>> > next release, unless the fix is simple (just a change of API).
>>
>> I took a brief look at it, and from the errors I have seen, one is
>> cosmetic, the other one is a bit more involved (rewriting
>> PyArray_Scalar unicode support). While it is not difficult in nature,
>> the current code has multiple #ifdef of Py_UNICODE_WIDE, meaning it
>> would require multiple configurations on multiple python versions to
>> be tested.
>>
>> I don't think python 3.3 support is critical - people who want to play
>> with bet interpreters can build numpy by themselves from master, so I
>> am -1 on integrating this into 1.7.
>>
>> I may have a fix within tonight for it, though,
>
>
> There are 2 tickets about this:
> http://projects.scipy.org/numpy/ticket/2145
> http://projects.scipy.org/numpy/ticket/1471

I am currently working on a PR trying to fix the unicode failures:

https://github.com/numpy/numpy/pull/366

It's a work in progress, I am still have some little issues, see the
PR for up-to-date details.

Ondrej