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 | schuppenies |
|---|---|
| Recipients | amaury.forgeotdarc, benjamin.peterson, facundobatista, schuppenies |
| Date | 2008年06月27日.09:05:37 |
| SpamBayes Score | 0.12522028 |
| Marked as misclassified | No |
| Message-id | <1214557539.48.0.656616714887.issue3122@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I was refering to the fact that something on the C level is cached without the Python user ever noticing that it wasn't there before. Caching itself is no criteria, but allocating memory without giving the user a chance to find out should be (in this context). Maybe I am missing something here, but calling match.regs creates a tuple which is not there before, but cannot be removed afterwards. This is why I handled it separately. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月27日 09:05:39 | schuppenies | set | spambayes_score: 0.12522 -> 0.12522028 recipients: + schuppenies, facundobatista, amaury.forgeotdarc, benjamin.peterson |
| 2008年06月27日 09:05:39 | schuppenies | set | spambayes_score: 0.12522 -> 0.12522 messageid: <1214557539.48.0.656616714887.issue3122@psf.upfronthosting.co.za> |
| 2008年06月27日 09:05:38 | schuppenies | link | issue3122 messages |
| 2008年06月27日 09:05:37 | schuppenies | create | |