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 lambertv
Recipients ezio.melotti, lambertv, ncoghlan, pitrou, vstinner
Date 2013-08-22.23:57:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377215846.58.0.25075626571.issue18623@psf.upfronthosting.co.za>
In-reply-to
Content
I have included a patch that moves _SuppressCoreFiles into test.support and a test that checks whether resource.RLIMIT_CORE is being properly set and reset. It would be nice if there was a more explicit way to test the creation of core files, however.
The patch also corrects a comment that stated ulimit was being set to (0, 0) when in the code only the soft limit was being set to 0. I'm pretty sure that the later should be done because then we don't run into trouble when we have to restore the hard limit to its original (higher) limit.
History
Date User Action Args
2013-08-22 23:57:27lambertvsetrecipients: + lambertv, ncoghlan, pitrou, vstinner, ezio.melotti
2013-08-22 23:57:26lambertvsetmessageid: <1377215846.58.0.25075626571.issue18623@psf.upfronthosting.co.za>
2013-08-22 23:57:26lambertvlinkissue18623 messages
2013-08-22 23:57:26lambertvcreate