Py3k status update #10
This is the tenth status update about our work on the py3k branch, which we
can work on thanks to all of the people who donated to the py3k proposal.
There's been significant progress since the last update: the linux x86-32
buildbot now passes 289 out of approximately 354 modules (with 39 skips) of
CPython's regression test suite.
That means there's only 26 test module failures left! The list of major items
remaining for 3.2 compatibility are now short enough to list here, with their
- Tokenizer support for non-ascii identifiers
- memoryview (Manuel Jacob's tackling this on the py3k-memoryview branch)
- multiprocessing module currently deadlocks
- Buggy handling of the new extended unpacking syntax by the compiler:
- The new Global Interpreter Lock and new thread signal handling
- Upgrade unicodedata to 6.0.0 (requires updates to the actual unicodedata
- test_capi (currently crashes)
- Update int's hash code to match to CPython (float's is already updated on the
py3k-newhash branch. note that PyPy 2.x doesn't even totally match
- test_sqlite (a new cffi based version seems to be coming)
Additionally there are still a number of failures in PyPy's internal test
suite. These tests are usually ran against untranslated versions of PyPy during
development. However we've now began running them against a fully translated
version of PyPy on the buildbot too (thanks to Amaury for setting this
up). This further ensures that our tests and implementation are sane.
We're getting closer to producing an initial alpha release. Before that happens
we'd like to see:
- further test fixes
- the results of test runs on other major platforms (e.g. linux x86-64 and osx
seem to have some additional failures as of now)
- some basic real world testing
Finally I'd like to thank Manuel Jacob for his various contributions over the
past month, including fixing the array and ctypes modules among other things,
and also Amaury Forgeot d'Arc for his ongoing excellent contributions.
A chart with failing tests over time would be cool. Or, just work on fixing those tests! :-)
That’s really, really, REALLY COOL!
Cool. How many errors have been fixed in current update? Is there any log available?