[issue41313] sys.setrecursionlimit: OverflowError still raised when int limited in sys.maxsize

[Stefan Krah]

Stefan Krah  added the comment:

Mark has already mentioned that setting the recursion limit to a
value higher than 2000-1 makes no sense.

Apart from that, sys.maxsize is actually documented like this:

   maxsize -- the largest supported length of containers.


So it applies to Py_ssize_t (signed version of size_t), but not to
any C integer in general.

--
nosy: +skrah
stage:  -> resolved
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41313] sys.setrecursionlimit: OverflowError still raised when int limited in sys.maxsize

[Mark Dickinson]

Mark Dickinson  added the comment:

Setting to pending; I don't see any bug here, and I suspect the original report 
was based on a misunderstanding of what sys.setrecursionlimit is for.

--
resolution:  -> not a bug
status: open -> pending

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41313] sys.setrecursionlimit: OverflowError still raised when int limited in sys.maxsize

[Eric V. Smith]

Change by Eric V. Smith :


--
title: OverflowError still raised when int limited in sys.maxsize -> 
sys.setrecursionlimit: OverflowError still raised when int limited in 
sys.maxsize

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com