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 | gvanrossum |
|---|---|
| Recipients | benjamin.peterson, gvanrossum |
| Date | 2008年03月18日.00:34:37 |
| SpamBayes Score | 0.006574548 |
| Marked as misclassified | No |
| Message-id | <1205800496.98.0.42440384501.issue2374@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I'll review this. My hunch is that we don't need this -- 2to3 takes care of this so there is no reason to tell people to change their code by hand. (You may notice a pattern -- things that 2to3 can fix easily generally don't deserve -3 warnings or backports, *unless* the backported feature adds significant functionality that's not easily available otherwise in 2.x.) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月18日 00:34:57 | gvanrossum | set | spambayes_score: 0.00657455 -> 0.006574548 recipients: + gvanrossum, benjamin.peterson |
| 2008年03月18日 00:34:57 | gvanrossum | set | spambayes_score: 0.00657455 -> 0.00657455 messageid: <1205800496.98.0.42440384501.issue2374@psf.upfronthosting.co.za> |
| 2008年03月18日 00:34:37 | gvanrossum | link | issue2374 messages |
| 2008年03月18日 00:34:37 | gvanrossum | create | |