[pypy-dev] setrecursionlimit deprecation?

[Alex Gaynor]

On Sat, Dec 11, 2010 at 1:16 PM, 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).
>
> Also, we should maybe change the class of the Warning. IIRC,
> DeprecationWarning is going to be ignored by default on python2.7, which
> means
> that most people won't see the warning at all once we merge fast-forward.
>
> ciao,
> Anto
> _______________________________________________
> pypy-dev at codespeak.net
> http://codespeak.net/mailman/listinfo/pypy-dev
>


Indeed, perhaps RuntimeWarning is more approrpiate?

-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
"Code can always be simpler than you think, but never as simple as you want"
-- Me
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20101211/dc31592e/attachment.html>