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 | mgiuca |
|---|---|
| Recipients | loewis, mgiuca, orsenthil, thomaspinckney3 |
| Date | 2008年07月10日.16:13:03 |
| SpamBayes Score | 0.0012417234 |
| Marked as misclassified | No |
| Message-id | <1215706384.14.0.192659013615.issue3300@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Setting Version back to Python 3.0. Is there a reason it was set to Python 3.1? This proposal will certainly break a lot of code. It's *far* better to do it in the big backwards-incompatible Python 3.0 release than a later release. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月10日 16:13:04 | mgiuca | set | spambayes_score: 0.00124172 -> 0.0012417234 recipients: + mgiuca, loewis, orsenthil, thomaspinckney3 |
| 2008年07月10日 16:13:04 | mgiuca | set | spambayes_score: 0.00124172 -> 0.00124172 messageid: <1215706384.14.0.192659013615.issue3300@psf.upfronthosting.co.za> |
| 2008年07月10日 16:13:03 | mgiuca | link | issue3300 messages |
| 2008年07月10日 16:13:03 | mgiuca | create | |