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 ngie
Recipients ngie, purcell, rhettinger
Date 2009-03-23.09:11:09
SpamBayes Score 4.3987834e-06
Marked as misclassified No
Message-id <>
I agree with you guys to a certain extent, but doing so only complicates
my setup procedure to the extent that I'm calling a lot of my teardown
code in a dumb manner, unless I actually kept track of how far into the
setup process I got before everything went awry and split it into a
multistep rollback process for atomicity.

This in and of itself seems like a lot to track with complicated
processes like configuring a daemon interactively via pexpect, or
modifying a remote VM instance with multiprocessing being used for
injection, and I don't know if I can expect consumers of my test suites
to get it right twice.

Could you guys provide some examples of existing test suites where this
may potentially break things?

Date User Action Args
2009-03-23 09:11:12ngiesetrecipients: + ngie, rhettinger, purcell
2009-03-23 09:11:12ngiesetmessageid: <>
2009-03-23 09:11:11ngielinkissue5538 messages
2009-03-23 09:11:10ngiecreate