[Numpy-discussion] Py3 merge

Charles R Harris charlesr.harris@gmail....
Sat Dec 5 20:30:43 CST 2009


On Sat, Dec 5, 2009 at 7:18 PM, Charles R Harris
<charlesr.harris@gmail.com>wrote:

>
>
> On Sat, Dec 5, 2009 at 5:41 PM, Pauli Virtanen <pav@iki.fi> wrote:
>
>> Hi,
>>
>> I'd like to commit my Py3 Numpy branch to SVN trunk soon:
>>
>>        http://github.com/pv/numpy-work/commits/py3k
>>
>> For an overview, check the notes:
>>
>>        http://github.com/pv/numpy-work/blob/py3k/doc/Py3K.txt
>>
>>
> That's a nice set of notes, very informative.
>
>
>> None of the changes should affect behavior on Py2. The test status
>> currently is:
>>
>>        Python 3.1:
>>        Ran 1964 tests in 10.294s
>>        FAILED (KNOWNFAIL=5, errors=435, failures=74)
>>
>>
> Heh, at least we are far enough along to get errors and failures.
>
>
>>        Python 2.4:
>>        Ran 2480 tests in 18.209s
>>        OK (KNOWNFAIL=4, SKIP=2)
>>
>>        Python 2.5:
>>        Ran 2483 tests in 18.552s
>>        OK (KNOWNFAIL=4)
>>
>>        Python 2.6:
>>        Ran 2484 tests in 20.359s
>>        OK (KNOWNFAIL=5)
>>
>> The next TODOs are:
>>
>> - Map 'S' scalartype to 'U' on Py3, and add a new scalartype for bytes
>> - Finish the rest of the PyString transition
>> - Fix I/O
>> - Hammer out causes for test failures
>>
>>
> We need character arrays for the astro people. I assume these will be byte
> arrays. Maybe Michael will weigh in here.
>
>
>> More TODOs are listed in Py3K.txt.
>>
>>
> Work, work, work. Great start.
>
>
PS, I wonder if it would be useful to keep the detailed info on the new type
structures in a supplementary file. They might be useful to someone else as
I had to dig through the Py3k sources to get them.

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20091205/4ab7a766/attachment.html 


More information about the NumPy-Discussion mailing list