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 ncoghlan
Recipients Mark.Shannon, ag6502, amaury.forgeotdarc, benjamin.peterson, francismb, ggenellina, ncoghlan, pitrou, serhiy.storchaka, terry.reedy
Date 2012-11-04.09:37:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1352021825.95.0.66102577565.issue5765@psf.upfronthosting.co.za>
In-reply-to
Content
We want to minimise the risk of breaking working code. Making it easy to adjust this recursion limit separately from the main recursion limit by using a scaling factor is a good way to do that. It shouldn't increase the maintenance burden in any significant way, since the ratio of the stack depth increase in the compiler vs the main interpreter loop should be relatively constant across platforms.

Autogenerated code could easily hit the 1000 term limit - if anything, I'd be inclined to set it *higher* than 4 rather than lower, as breaking previously working code in a maintenance release is a bad thing, regardless of our opinion of the sanity of that code.
History
Date User Action Args
2012-11-04 09:37:06ncoghlansetrecipients: + ncoghlan, terry.reedy, amaury.forgeotdarc, ggenellina, pitrou, ag6502, benjamin.peterson, Mark.Shannon, francismb, serhiy.storchaka
2012-11-04 09:37:05ncoghlansetmessageid: <1352021825.95.0.66102577565.issue5765@psf.upfronthosting.co.za>
2012-11-04 09:37:05ncoghlanlinkissue5765 messages
2012-11-04 09:37:05ncoghlancreate