[pypy-dev] setrecursionlimit deprecation?

Benjamin Peterson benjamin at python.org
Sat Dec 11 21:52:11 CET 2010


2010/12/11 Paolo Giarrusso <p.giarrusso at gmail.com>:
> On Sat, Dec 11, 2010 at 19:16, Antonio Cuni <anto.cuni at gmail.com> wrote:
>> On 11/12/10 18:32, Armin Rigo wrote:
>>
>>> But then people are going to complain that their app seems to hang up
>>> on pypy, and neither they nor we have any clue what is going on ---
>>> until we figure out that they used sys.setrecursionlimit() to put a
>>> bound on recursion and catch the RuntimeError.  That's at least the
>>> reason for which I suggested that calling sys.setrecursionlimit()
>>> should at least print a warning.  Now I agree that maybe the message
>>> of the warning is not the clearest one.
>
>> I was about to propose to change the message into something like
>> "sys.setrecursionlimit is ignored by PyPy".  I think this is already an
>> improvement over the current message, but has the drawback than then people
>> will complain that pypy might run out of stack (which is false, but not
>> apparent by the warning message).
>
> Do you mean that the stack size on Python is not limited (which has
> its problems for infinite-recursion bugs), or just that stack overflow
> is handled gracefully by throwing an exception?

The latter.


-- 
Regards,
Benjamin



More information about the Pypy-dev mailing list