On Sat, Dec 5, 2009 at 5:41 PM, Pauli Virtanen <p...@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. Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion