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 rhettinger
Recipients alex, amaury.forgeotdarc, arigo, benjamin.peterson, ezio.melotti, python-dev, rhettinger, serhiy.storchaka
Date 2013-04-06.19:54:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Isn't it exactly what Py_EnterRecursiveCall does?

No, it isn't.  Py_EnterRecursiveCall() counts calls and measures depth.  It is sprinked all over the source code, everywhere a potentially recursive call could be made.  

Instead, it would be nice if the interpreter could monitor the actual stack size and take appropriate actions when it is running low on space.  The would save us from putting in expensive fine grained checks throughout the source code.
Date User Action Args
2013-04-06 19:54:30rhettingersetrecipients: + rhettinger, arigo, amaury.forgeotdarc, benjamin.peterson, ezio.melotti, alex, python-dev, serhiy.storchaka
2013-04-06 19:54:30rhettingersetmessageid: <>
2013-04-06 19:54:30rhettingerlinkissue14010 messages
2013-04-06 19:54:30rhettingercreate