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:04:30 |
| SpamBayes Score | 0.002655331 |
| Marked as misclassified | No |
| Message-id | <1209535472.82.0.582683298988.issue2719@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
ISTM, the only value added by next(g) is that it replaces g.next() with a more conventional spelling, g.__next__(). Since 2.6 still has g.next (),I don't see how this backport adds value. It does however create a second way to do it that will be confusing to some remaining in the 2.x world. I think we should avoid double spellings in 2.6 except in cases where the 2-to-3 converter would need help. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年04月30日 06:04:33 | rhettinger | set | spambayes_score: 0.00265533 -> 0.002655331 recipients: + rhettinger, gvanrossum, georg.brandl |
| 2008年04月30日 06:04:32 | rhettinger | set | spambayes_score: 0.00265533 -> 0.00265533 messageid: <1209535472.82.0.582683298988.issue2719@psf.upfronthosting.co.za> |
| 2008年04月30日 06:04:31 | rhettinger | link | issue2719 messages |
| 2008年04月30日 06:04:31 | rhettinger | create | |