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 | brett.cannon |
|---|---|
| Recipients | ajaksu2, amaury.forgeotdarc, brett.cannon, nnorwitz, theller |
| Date | 2008年04月05日.15:32:02 |
| SpamBayes Score | 0.055485774 |
| Marked as misclassified | No |
| Message-id | <1207409523.23.0.0484852685798.issue2548@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Neal has the memory of an elephant or something. Yes, I dealt with a similar issue where the recursion limit was hit, but then normalizing the exception just caused it to hit it again. I thought I changed it such that normalizing an exception actually turned off the depth check or to raise a pre-defined exception for the recursion depth limit. I don't have time to look at this right now (still on holiday in Brussels), but if I remember correctly the last time this came up I liked the pre-allocated recursion limit exception. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年04月05日 15:32:03 | brett.cannon | set | spambayes_score: 0.0554858 -> 0.055485774 recipients: + brett.cannon, nnorwitz, theller, amaury.forgeotdarc, ajaksu2 |
| 2008年04月05日 15:32:03 | brett.cannon | set | spambayes_score: 0.0554858 -> 0.0554858 messageid: <1207409523.23.0.0484852685798.issue2548@psf.upfronthosting.co.za> |
| 2008年04月05日 15:32:02 | brett.cannon | link | issue2548 messages |
| 2008年04月05日 15:32:02 | brett.cannon | create | |