➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients benjamin.peterson, eric.araujo, georg.brandl, kontinuity, ned.deily, ronaldoussoren, srid, stoneyb, tarek
Date 2011-05-07.06:34:24
SpamBayes Score 3.0021315e-08
Marked as misclassified No
Message-id <1304750066.68.0.770885016003.issue9516@psf.upfronthosting.co.za>
In-reply-to
Content 
I've attached a v2 of the patch which adresses Éric's comments.

I haven't changed the CompileError handling though, that would change a test failure into a test error. IMHO test errors should only happend due to bugs in the test code.

AddCleanup is neat trick, I keep forgetting the nice new features that were added to unittest recently.

The assertEquals issue is one that keeps biting me, I know the correct form is assertEqual but every single time I write tests I keep using assertEquals for some reason.  Maybe its time for some electroshock therapy...
History
Date User Action Args
2011-05-07 06:34:26ronaldoussorensetrecipients: + ronaldoussoren, georg.brandl, benjamin.peterson, tarek, ned.deily, eric.araujo, srid, stoneyb, kontinuity
2011-05-07 06:34:26ronaldoussorensetmessageid: <1304750066.68.0.770885016003.issue9516@psf.upfronthosting.co.za>
2011-05-07 06:34:25ronaldoussorenlinkissue9516 messages
2011-05-07 06:34:25ronaldoussorencreate