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 | pitrou |
|---|---|
| Recipients | benjamin.peterson, brett.cannon, esrever_otua, pitrou, trent |
| Date | 2008年07月17日.20:06:59 |
| SpamBayes Score | 0.0038706693 |
| Marked as misclassified | No |
| Message-id | <1216325224.0.0.88699473161.issue3373@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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 stopped at 250 With 2.5, the output is: rec1 stopped at 1000 rec2 stopped at 1000 rec3 stopped at 500 rec4 stopped at 1000 rec5 stopped at 1000 rec6 stopped at 1000 I think we should just acknowledge that recursion count has gotten stricter (PyObject_Call() increases it, and then PyEval_EvalFrameEx() will increase it a second time if Python code is entered), and bump the default recursion limit. (the reason calling Python functions directly doesn't increase the recursion count twice is that there are optimization shortcuts in ceval.c to avoid calling PyObject_Call() - not the case though when calling a type object) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月17日 20:07:04 | pitrou | set | spambayes_score: 0.00387067 -> 0.0038706693 recipients: + pitrou, brett.cannon, esrever_otua, benjamin.peterson, trent |
| 2008年07月17日 20:07:04 | pitrou | set | spambayes_score: 0.00387067 -> 0.00387067 messageid: <1216325224.0.0.88699473161.issue3373@psf.upfronthosting.co.za> |
| 2008年07月17日 20:07:02 | pitrou | link | issue3373 messages |
| 2008年07月17日 20:07:01 | pitrou | create | |