On Tue, Aug 7, 2012 at 6:33 AM, Armin Rigo <ar...@tunes.org> wrote: > If you can come up with a more precise scheme, you're welcome. The > issue is to know when it's ok to reserve from that pool and when we > should raise an RPython MemoryError instead. A possible answer would > look like "when allocating internal vs user objects", for some > unspecified-yet distinction of internal vs user objects.
Would having all allocations inside an except MemoryError: block be eligible to use the reserved pool be workable? Or perhaps "inside an except: block, while a MemoryError is the current exception"? It might even be ok to just have it be "while inside an except: block". To my naive eyes, it seems like something simple like one of the above would handle the normal use cases, and allow for some real-world use to provide information about if the criteria need tightening, etc. Cheers, Eli _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
