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 | Rhamphoryncus |
|---|---|
| Recipients | Rhamphoryncus, belopolsky, duncanb, facundobatista, terry.reedy |
| Date | 2008年03月19日.16:19:49 |
| SpamBayes Score | 0.015588567 |
| Marked as misclassified | No |
| Message-id | <1205943590.53.0.531357089518.issue2417@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The original bug is not whether or not python reuses int objects, but rather that an existing optimization disappears under certain circumstances. Something is breaking our optimization. The later cases where the optimization is simply gone in 3.0a3 are more difficult. We don't *have* to keep them.. but we probably want them. The small int reuse happens for a reason. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月19日 16:19:50 | Rhamphoryncus | set | spambayes_score: 0.0155886 -> 0.015588567 recipients: + Rhamphoryncus, duncanb, terry.reedy, facundobatista, belopolsky |
| 2008年03月19日 16:19:50 | Rhamphoryncus | set | spambayes_score: 0.0155886 -> 0.0155886 messageid: <1205943590.53.0.531357089518.issue2417@psf.upfronthosting.co.za> |
| 2008年03月19日 16:19:49 | Rhamphoryncus | link | issue2417 messages |
| 2008年03月19日 16:19:49 | Rhamphoryncus | create | |