➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients Wheerd, benjamin.peterson, brett.cannon, ncoghlan, paul.moore, pitrou, scoder, serhiy.storchaka, steve.dower, terry.reedy, tim.golden, yselivanov, zach.ware
Date 2017-08-05.05:09:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1501909769.11.0.91670228829.issue31113@psf.upfronthosting.co.za>
In-reply-to
Content 
I concur with Stefan. Some parts of the compiler are recursive. The crash is expected for enough complex programs, and the size of C stack is platform depended. There are few hard-coded limits (MAXINDENT, CO_MAXBLOCKS) that may prevent the crash by converting it to exception, but they don't take role in this case (MAXINDENT is too large (100), and CO_MAXBLOCKS limits only the level of nested "for" and "try" blocks).

sys.setrecursionlimit doesn't have relation to C stack.

Increasing the size of C stack on Windows can solve this issue for this particular case.
History
Date User Action Args
2017-08-05 05:09:29serhiy.storchakasetrecipients: + serhiy.storchaka, brett.cannon, terry.reedy, paul.moore, ncoghlan, pitrou, scoder, tim.golden, benjamin.peterson, zach.ware, yselivanov, steve.dower, Wheerd
2017-08-05 05:09:29serhiy.storchakasetmessageid: <1501909769.11.0.91670228829.issue31113@psf.upfronthosting.co.za>
2017-08-05 05:09:29serhiy.storchakalinkissue31113 messages
2017-08-05 05:09:28serhiy.storchakacreate