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 mhammond
Recipients amaury.forgeotdarc, kristjan.jonsson, loewis, mhammond
Date 2009-02-01.11:01:07
SpamBayes Score 4.1992153e-05
Marked as misclassified No
Message-id <1233486079.41.0.480347232493.issue4804@psf.upfronthosting.co.za>
In-reply-to
Content
Fair enough - but assertions are still disabled while your "reference
count" is >0, which is still while other arbitrary code is running. 
While I agree this is an improvement, I'm afraid I'm not playing close
enough attention to understand why your patch is better than, eg, simply
disabling such assertions globally during the test run. Given the patch
in issue5116, this could be implemented in far less lines of code -
certainly less intrusive lines.  Would this not achieve the same result?
History
Date User Action Args
2009-02-01 11:01:19mhammondsetrecipients: + mhammond, loewis, amaury.forgeotdarc, kristjan.jonsson
2009-02-01 11:01:19mhammondsetmessageid: <1233486079.41.0.480347232493.issue4804@psf.upfronthosting.co.za>
2009-02-01 11:01:08mhammondlinkissue4804 messages
2009-02-01 11:01:07mhammondcreate