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 michael.foord
Recipients Julian, brett.cannon, chris.jerdonek, daniel.urban, eric.araujo, ezio.melotti, michael.foord, pablomouzo, r.david.murray
Date 2012-09-19.14:49:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1348066141.32.0.0312746051513.issue11664@psf.upfronthosting.co.za>
In-reply-to
Content
I think those guidelines are horrible and I've told the pyramid folks that.

There is a related issue for unittest that failing to import a test module (due to a failed import in the test module for example) should not kill the test run but should create a "failing test" that shows the problem.

This is all wandering off topic however...
History
Date User Action Args
2012-09-19 14:49:01michael.foordsetrecipients: + michael.foord, brett.cannon, ezio.melotti, eric.araujo, r.david.murray, pablomouzo, daniel.urban, chris.jerdonek, Julian
2012-09-19 14:49:01michael.foordsetmessageid: <1348066141.32.0.0312746051513.issue11664@psf.upfronthosting.co.za>
2012-09-19 14:49:00michael.foordlinkissue11664 messages
2012-09-19 14:49:00michael.foordcreate