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 memeplex
Recipients dstufft, eric.araujo, memeplex
Date 2016-03-11.17:56:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1457718997.42.0.688813904458.issue26541@psf.upfronthosting.co.za>
In-reply-to
Content
The current implementation offers a stop_after parameter for run_setup() but not for setup(). This design has some shortcomings:

1. It couples the possibility to stop setup after some phase to the fact that the setup function resides in another file. But the feature is also useful when directly invoking setup (for example, if you want to tweak the dist before running it).

2. The other parameters to run_setup are already parameters to setup. It would be more consistent to make all three parameters common to both methods.

3. Arguably messy global variable manipulation to communicate run_setup and setup.
History
Date User Action Args
2016-03-11 17:56:37memeplexsetrecipients: + memeplex, eric.araujo, dstufft
2016-03-11 17:56:37memeplexsetmessageid: <1457718997.42.0.688813904458.issue26541@psf.upfronthosting.co.za>
2016-03-11 17:56:37memeplexlinkissue26541 messages
2016-03-11 17:56:37memeplexcreate