|
Size: 2008
Comment:
|
Size: 1646
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| * test_coercion - __cmp__ doesn't utilize __coerce__? | * test_builtin - may still have parse problems, mostly other issues |
| Line 8: | Line 8: |
| * test_generators - not rejecting incorrect syntax wrt yield; but others need to be resolved outside of parser (maybe eval order?); fibgen is causing parse issues; tracebacks have extra blank lines apparently * test_genexps - need to test iterability of an object like int; similar syntax issues as test_generator |
* test_generators - tracebacks have extra blank lines apparently; different syntax errors causing doctest to reject; GC dependencies; also parser probs |
| Line 11: | Line 10: |
| * test_list, test_userlist - test_set_subscript | |
| Line 15: | Line 15: |
| * test_tempfile - 1 failure, test_usable_template * test_unicode - lack of idna encoding (which needs unicodedata) |
* test_unicode - no idna encoding (which needs unicodedata); raises wrong error for decode to int of unicode string |
| Line 18: | Line 17: |
| * test_with - we're generating bad bytecode with nested yields, e.g. with manager(): yield 1 (testWithYields) | * test_with - 1 failure, testNestedSingleStatements (__main__.ExceptionalTestCase), this is a tricky one |
| Line 24: | Line 23: |
| * test_scope - sometimes fails due to GC | * test_scope - sometimes fails due to GC - is this still the case? |
| Line 31: | Line 30: |
| * test_builtin - compile/exec/eval problems * test_compile - over acceptance of incorrect syntax; need to raise problems with unicode being declared to have an encoding! * test_contextlib - likely parser eval order * test_decorators - eval order * test_future - bad line numbers * test_genexp, test_generator - parser probs * test_java_integration - ReservedNamesTest (in/exec), also there's class * test_jy_compile - not rejecting syntax, is there an issue with exec code in a_dict? |
* test_compiler - one line functions are not working compiler.parse (causing AttributeError: 'NoneType' object has no attribute 'suite') * test_decorators - compile(..., "eval") not working for test_dbcheck |
To Fix
- test_builtin - may still have parse problems, mostly other issues
- test_doctest - unicode problem
- test_generators - tracebacks have extra blank lines apparently; different syntax errors causing doctest to reject; GC dependencies; also parser probs
- test_inspect
- test_list, test_userlist - test_set_subscript
- test_multibytecodec
- test_multibytecodec_support
- test_site - del sys.setdefaultencoding does nothing
- test_struct - needs new 2.5 struct.Struct type and pack_into/unpack_from
- test_unicode - no idna encoding (which needs unicodedata); raises wrong error for decode to int of unicode string
- test_univnewlines - test_doctest failures don't restore sys.stdin -- causes to skip (it normally passes)
- test_with - 1 failure, testNestedSingleStatements (__main__.ExceptionalTestCase), this is a tricky one
- test_zipfile - possibly struct issues?
Flaky/arch?
- test_scope - sometimes fails due to GC - is this still the case?
- test_socket - historically this is the case on SO_RCVBUF, SO_SNDBUF
- test_tuple - sometimes OutOfMemoryErrors during regrtest (when creating a set from a large list of small tuples). maybe not the tests fault, but the fact that the regrtest progressively uses more and more memory as it goes: http://pylonshq.com/pasties/917
Parser
- test_compiler - one line functions are not working compiler.parse (causing AttributeError: 'NoneType' object has no attribute 'suite')
- test_decorators - compile(..., "eval") not working for test_dbcheck
Development
- test__rawffi (for ctypes, ported from PyPy)