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 | eric.smith |
|---|---|
| Recipients | eric.smith |
| Date | 2008年03月20日.19:08:18 |
| SpamBayes Score | 0.49962807 |
| Marked as misclassified | No |
| Message-id | <1206040099.45.0.826679091629.issue2436@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Should this be accepted in 3.0, and become a no-op: from __future__ import print_function ? It might make using code in 2.6 and 3.0 easier, since you would not have to delete this line. I note that: from __future__ import with_statement is already valid in 3.0. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月20日 19:08:19 | eric.smith | set | spambayes_score: 0.499628 -> 0.49962807 recipients: + eric.smith |
| 2008年03月20日 19:08:19 | eric.smith | set | spambayes_score: 0.499628 -> 0.499628 messageid: <1206040099.45.0.826679091629.issue2436@psf.upfronthosting.co.za> |
| 2008年03月20日 19:08:18 | eric.smith | link | issue2436 messages |
| 2008年03月20日 19:08:18 | eric.smith | create | |