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 | rhettinger |
|---|---|
| Recipients | georg.brandl, gvanrossum, rhettinger |
| Date | 2008年04月30日.06:37:17 |
| SpamBayes Score | 0.08888872 |
| Marked as misclassified | No |
| Message-id | <1209537444.6.0.00305789678274.issue2719@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The problem is with the "if you use it consistently" premise. That will not hold in an environment with legacy code, multiple programmers, lots of code in ASPN recipes and published materials, and third-party modules. A patch like this dooms Py2.6 programmers to seeing both of these forms intermixed throughout the code base. This is *not* a win. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年04月30日 06:37:26 | rhettinger | set | spambayes_score: 0.0888887 -> 0.08888872 recipients: + rhettinger, gvanrossum, georg.brandl |
| 2008年04月30日 06:37:24 | rhettinger | set | spambayes_score: 0.104833 -> 0.0888887 messageid: <1209537444.6.0.00305789678274.issue2719@psf.upfronthosting.co.za> |
| 2008年04月30日 06:37:23 | rhettinger | link | issue2719 messages |
| 2008年04月30日 06:37:20 | rhettinger | create | |