Antoine,
All the cases I could find would be more "test" than "use" cases. Given
that most ways to abort I find in 3.0 are related to "undetected error"s
in trunk, I'm almost convinced that 3.0 is right here :)
My last worry is that it'd be kinda easy to get Fatal errors from
sane-ish functions and deeply nested input:
============
class rec:
def __str__(self):
return str(self)
def overflower(x):
try:
return overflower(x)
except:
print (x)
list_rec = [100000000001]
for _ in range(12): list_rec = [[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[
[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[list_rec]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
str_rec = rec()
overflower(1) # OK
overflower(list_rec) # Aborts
overflower(str_rec) # Aborts
============
Thanks for the feedback!
Attached is a file that shows how trunk is doing something weird when it
works (besides the other reported issues that arise from that).