If you read the comment that goes with the code snippet pasted in the original email it makes far more sense as the author is talking specifically about out of memory errors...
"You already got excellent answers, I just wanted to add one more tip that's served me well over the years in a variety of language for the specific problem "how to cleanly diagnose, log, etc, out of memory errors?". Problem is, if your code gets control before enough objects have been destroyed and their memory recycled, memory might be too tight to do propert logging, gui work, etc, etc -- how do we ensure this doesn't happen? Answer: build an emergency stash so you know you can spend it in such emergencies: rainydayfund = [[] for x in xrange(16*1024)] # or however much you need def handle_exception(e): global rainydayfund del rainydayfund ... etc, etc ... " - Alex Martelli -- James _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
