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 ctheune
Recipients ctheune, gvanrossum
Date 2012-11-01.13:15:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1351775704.44.0.517582874178.issue16381@psf.upfronthosting.co.za>
In-reply-to
Content
I run long-running server processes (web apps, etc) a lot and I keep encountering the situation that many applications will not properly deal with MemoryError exceptions but end up in an unusable state.

From an operational perspective I wish the process in this case would just fail and exit.

I talked to Guido about this general idea at EuroPython2012 and he encouraged me to look into this. 

Here's a patch:
https://bitbucket.org/ctheune/cpython/changeset/323bb572344d46df669d3dbec4431cf6720fc5b4

I think it does what I want it to do, but a) my C knowledge is really bad and b) I'm not sure whether this is the right approach anyway.

I'd appreciate feedback and possibly inclusion in the core.
History
Date User Action Args
2012-11-01 13:15:04ctheunesetrecipients: + ctheune, gvanrossum
2012-11-01 13:15:04ctheunesetmessageid: <1351775704.44.0.517582874178.issue16381@psf.upfronthosting.co.za>
2012-11-01 13:15:04ctheunelinkissue16381 messages
2012-11-01 13:15:03ctheunecreate