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 takluyver
Recipients The Compiler, cjw296, michael.foord, ncoghlan, pstch, takluyver, yselivanov
Date 2017-05-22.19:12:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1495480343.98.0.651982847576.issue25532@psf.upfronthosting.co.za>
In-reply-to
Content
I could go either way on that. It's not hard to imagine it as a recursive algorithm, and using the recursion limit provides a simple configuration escape hatch if someone has a desperate need for something wrapped 3000 times for some strange reason. But it may also be somewhat surprising if someone sets a really high recursion limit and suddenly it behaves oddly.

I've made the PR with getrecursionlimit() for now, but I'm happy to change it if people prefer it the other way.
History
Date User Action Args
2017-05-22 19:12:24takluyversetrecipients: + takluyver, ncoghlan, cjw296, michael.foord, yselivanov, The Compiler, pstch
2017-05-22 19:12:23takluyversetmessageid: <1495480343.98.0.651982847576.issue25532@psf.upfronthosting.co.za>
2017-05-22 19:12:23takluyverlinkissue25532 messages
2017-05-22 19:12:23takluyvercreate