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 jcea
Recipients Mark.Gius, gregory.p.smith, jcea, neologix
Date 2012-10-26.10:37:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1351247848.69.0.50082867268.issue16327@psf.upfronthosting.co.za>
In-reply-to
Content
The problem with using RLIMIT is that the testsuite could be executing several tests in parallel using independent threads, for instance. You don't want to influence unrelated tests.

Overiding private methods is ugly, but if the code evolves the test would break, and the programmer just have to update it. I think that "sometimes" we have to be "practical". There are plenty of examples of this in the testsuite, using implementation details, etc.
History
Date User Action Args
2012-10-26 10:37:28jceasetrecipients: + jcea, gregory.p.smith, neologix, Mark.Gius
2012-10-26 10:37:28jceasetmessageid: <1351247848.69.0.50082867268.issue16327@psf.upfronthosting.co.za>
2012-10-26 10:37:28jcealinkissue16327 messages
2012-10-26 10:37:28jceacreate