[issue3373] sys recursion limit a lot shorter on trunk?

Antoine Pitrou [EMAIL PROTECTED] added the comment: (FWIW, I just ran Misc/find_recursion_limit.py on a 32-bit Windows box. With 2.6 I get 5900. With 3.0 I get 9000. So the good news is that 3.0 seems to be less stack-hungry :-)) ___ Python tracker [EMAIL

[issue3373] sys recursion limit a lot shorter on trunk?

Guido van Rossum [EMAIL PROTECTED] added the comment: I think it's fine as it is. Incrementing the stack level more frequently is a good thing since there used to be paths that didn't increment it at all and hence could cause segfaults. The default is conservative since increasing it could

[issue3373] sys recursion limit a lot shorter on trunk?

Benjamin Peterson [EMAIL PROTECTED] added the comment: Guido, can you comment? -- assignee: - gvanrossum nosy: +gvanrossum priority: high - release blocker ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3373

[issue3373] sys recursion limit a lot shorter on trunk?

Changes by Amaury Forgeot d'Arc [EMAIL PROTECTED]: -- nosy: +amaury.forgeotdarc ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3373 ___ ___

[issue3373] sys recursion limit a lot shorter on trunk?

Antoine Pitrou [EMAIL PROTECTED] added the comment: Here is a small script that shows various possibilities depending on how object creation is done, and here is the output with the trunk: rec1 stopped at 1000 rec2 stopped at 1000 rec3 stopped at 500 rec4 stopped at 334 rec5 stopped at 334 rec6

[issue3373] sys recursion limit a lot shorter on trunk?

Changes by Antoine Pitrou [EMAIL PROTECTED]: -- priority: - high versions: +Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3373 ___ ___

[issue3373] sys recursion limit a lot shorter on trunk?

Antoine Pitrou [EMAIL PROTECTED] added the comment: Why was 1000 chosen in the first place? If it's just an arbitrary value then we can bump it to 4000 so that people don't get bad surprises when upgrading their Python. This looks more like the interpreter is adding 4x the number of items to

[issue3373] sys recursion limit a lot shorter on trunk?

Brett Cannon [EMAIL PROTECTED] added the comment: On Wed, Jul 16, 2008 at 4:20 AM, Antoine Pitrou [EMAIL PROTECTED] wrote: Antoine Pitrou [EMAIL PROTECTED] added the comment: Why was 1000 chosen in the first place? If it's just an arbitrary value then we can bump it to 4000 so that people

[issue3373] sys recursion limit a lot shorter on trunk?

Benjamin Peterson [EMAIL PROTECTED] added the comment: Brett: It was originally 10,000, but people wanted thread switches to occur more often. I thought that was managed by sys.setcheckinterval. -- nosy: +benjamin.peterson ___ Python tracker [EMAIL

[issue3373] sys recursion limit a lot shorter on trunk?

Brett Cannon [EMAIL PROTECTED] added the comment: On Wed, Jul 16, 2008 at 11:28 AM, Benjamin Peterson [EMAIL PROTECTED] wrote: Benjamin Peterson [EMAIL PROTECTED] added the comment: Brett: It was originally 10,000, but people wanted thread switches to occur more often. I thought that was

[issue3373] sys recursion limit a lot shorter on trunk?

Darryl Dixon [EMAIL PROTECTED] added the comment: Hi Trent, No, my build did not invoke --with-pydebug. In other words, the process I used was simply: svn co http://svn.python.org/projects/python/trunk python-trunk cd python-trunk ./configure --prefix=/home/dixond/throwaway make make install

[issue3373] sys recursion limit a lot shorter on trunk?

New submission from Darryl Dixon [EMAIL PROTECTED]: The system recursion limit seems to be wildly different in its behaviour on 2.6/trunk versus, for example, 2.5 or 2.4, EG: On Python 2.4: Python 2.4.3 (#1, Dec 11 2006, 11:38:52) [GCC 4.1.1 20061130 (Red Hat 4.1.1-43)] on linux2 Type help,

[issue3373] sys recursion limit a lot shorter on trunk?

Brett Cannon [EMAIL PROTECTED] added the comment: A lot of crashers were fixed for 2.6 where the recursion limit was not being used at all. That is probably what you are seeing. -- nosy: +brett.cannon ___ Python tracker [EMAIL PROTECTED]