Bernie Hackett added the comment: > Well, Python has no perfect protection again stack overflow. It's only best > effect.
That's interesting. I thought there was a stronger contract, and it appeared that way in all previous cpython releases back to 2.4. Again, this failure is new with 3.5.0. > You should change sys.setrecursionlimit() to a lower limit to try to limit > the risk of a crash. That's a great suggestion and it appears to work around the issue, thanks. Feel free to close this won't fix, but given that this appears to be the second report of this issue for 3.5 (see issue22971) someone who understands interpreter internals may want to look into the problem a bit more first. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25222> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
