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 hpk
Recipients hpk, michael.foord, r.david.murray
Date 2010-12-06.19:06:13
SpamBayes Score 0.0051483493
Marked as misclassified No
Message-id <1291662375.96.0.872764569012.issue10548@psf.upfronthosting.co.za>
In-reply-to
Content
FWIW i tend to agree and would probably prefer setup/teardown to result in an error rather than be subsumed in an expected-to-fail marked test.  I guess if one regards setup/teardown as a place to implement pre/post-conditions than the changes suggested by Michael make more sense.  I'd like to see a more "real" use case / user than the abstract case provided here.
History
Date User Action Args
2010-12-06 19:06:16hpksetrecipients: + hpk, r.david.murray, michael.foord
2010-12-06 19:06:15hpksetmessageid: <1291662375.96.0.872764569012.issue10548@psf.upfronthosting.co.za>
2010-12-06 19:06:13hpklinkissue10548 messages
2010-12-06 19:06:13hpkcreate