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日.07:12:13 |
| SpamBayes Score | 0.07928958 |
| Marked as misclassified | No |
| Message-id | <1214550735.19.0.465039873317.issue3122@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
You are right, the rule is to not include referenced objects. But, and this has been rather informal up to now, I handled transparently cached information as something that is added to the memory used by an object (see unicode.defenc). The same I applied to MatchObject.regs. The rational being that the user cannot know wether the match positions are cached or not. What do you think? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月27日 07:12:15 | schuppenies | set | spambayes_score: 0.0792896 -> 0.07928958 recipients: + schuppenies, facundobatista, amaury.forgeotdarc, benjamin.peterson |
| 2008年06月27日 07:12:15 | schuppenies | set | spambayes_score: 0.0792896 -> 0.0792896 messageid: <1214550735.19.0.465039873317.issue3122@psf.upfronthosting.co.za> |
| 2008年06月27日 07:12:14 | schuppenies | link | issue3122 messages |
| 2008年06月27日 07:12:13 | schuppenies | create | |