➜

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 benjamin.peterson, christian.heimes, ctheune, ebfe, gvanrossum, hynek, jcea
Date 2013-03-17.20:35:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1363552549.77.0.550051601056.issue16381@psf.upfronthosting.co.za>
In-reply-to
Content 
I feel unsure how to help this move along. 

I agree that making it possible for applications to carefully work with MemoryErrors is a good idea. I don't think heuristics to determine which situation we are in will solve this but make it more spooky. (This is a semantic issue anyways).

My goal is to use the flag to make it easier for operators to deal with applications that don't get it right. This isn't to defend bad programming but to support temporary relief.
History
Date User Action Args
2013-03-17 20:35:49ctheunesetrecipients: + ctheune, gvanrossum, jcea, christian.heimes, benjamin.peterson, ebfe, hynek
2013-03-17 20:35:49ctheunesetmessageid: <1363552549.77.0.550051601056.issue16381@psf.upfronthosting.co.za>
2013-03-17 20:35:49ctheunelinkissue16381 messages
2013-03-17 20:35:49ctheunecreate