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 | schmir |
|---|---|
| Recipients | barry, gvanrossum, jhylton, loewis, schmir |
| Date | 2008年01月18日.11:32:52 |
| SpamBayes Score | 0.43920395 |
| Marked as misclassified | No |
| Message-id | <1200655974.29.0.636218491686.issue215555@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Well, I've been a victim of this one yesterday in a real world example. I'm logging the repr of arguments to XMLRPC method calls and we happen to use nested lists, which where deep enough to overflow that stack. It's now 8 years later and I can live with the parser using 60K memory. I think this limit should be upped a bit. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年01月18日 11:32:54 | schmir | set | spambayes_score: 0.439204 -> 0.43920395 recipients: + schmir, gvanrossum, loewis, jhylton, barry |
| 2008年01月18日 11:32:54 | schmir | set | spambayes_score: 0.439204 -> 0.439204 messageid: <1200655974.29.0.636218491686.issue215555@psf.upfronthosting.co.za> |
| 2008年01月18日 11:32:52 | schmir | link | issue215555 messages |
| 2008年01月18日 11:32:52 | schmir | create | |