test_file is fixed
remove bogus category
|Deletions are marked like this.||Additions are marked like this.|
|Line 133:||Line 133:|
List of tests that are failing in the py3k-struni branch
(Back to ["Python3000"].)
- if you start working on a test, to avoid duplicate work, add your name+email+date to the bulleted item for the test below, with the text "FIXING" or "INVESTIGATING"
- if you figure out why a test is failing, just add a note (name etc. is still appreciated)
- if you fix a test, and you check in the fix, add a note "FIXED" (occasionally we'll clean these up)
- if you don't have checkin permissions, use the SF patch manager and note the patch number here (perhaps in the form of a link to python.org/sf/NNNNN), and add a note "FIXED" (plus name etc.)
How to run tests
Assume you've got the py3k-struni branch checked out.
./configure make ./python Lib/test/regrtest.py test_foobar # runs test_foobar ./python Lib/test/test_foobar.py # for more detail about failures
test_aepack (OSX only)
test_applesingle (OSX only)
test_cProfile: not worth it? (I think this will be killed)
test_cpickle: not worth it? (I think this may be killed.)
test_macostools (OSX only)
test_plistlib (OSX only)
test_scriptpackages (OSX only)
test_sgmllib (passes on Ubuntu, fails on OSX)
test_uuid (passes on OSX, fails on Ubuntu)
test_wave: probably not worth fixing; aren't we going to delete this?
test_zipimport: lots of str/bytes issues, shouldn't be too hard; important