<LarstiQ>
so then RuntimErrors are also in general not safe to catch?
<cfbolz>
LarstiQ: no, it's specifically RecursionError
<LarstiQ>
but that's a a subclass so any RuntimError might be the unsafe RecursionError?
<cfbolz>
ah
<cfbolz>
maybe, yes
<phlebas>
cfbolz: isn't that a general issue with catching stack overflows in any system? the JVM has three different zones at the end of the stack to allow certain things to still work after stack overflows, but it's only ever improving your chances, you cannot assume in general that finally blocks will be run
<phlebas>
even in Squeak, where your stack is on your heap and a stack overflow is basically an out of memory, you can recover, but you cannot be sure that all `ensure:` blocks have run, since they may have run out of memory, too
<cfbolz>
phlebas: right
<cfbolz>
It should be documented
<cfbolz>
And we maybe want the 'several zones' approach
<cfbolz>
So it seem cpython does stuff like that already
<phlebas>
:D and mark opened a PR just 1 hour ago to fix it again
<iwkse>
mattip: thanks :)
<iwkse>
hi, do you know an efficient way to achieve something like this? https://bpa.st/KSQA Basically filtering by a key of an array of dictionaries
Joannah has joined #pypy
<iwkse>
this seems to work res = map(lambda x: {'a': x['a']}, a)
<Joannah>
I wonder if anyone knows a good way or can give an example of using a "xxx.a" link files with rffi. Examples given in this tutorial: https://mesapy.org/rpython-by-example/rffi/index.html are simple. In the PyPy code base, I only found a test case that is not as useful: