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 | georg.brandl |
|---|---|
| Recipients | georg.brandl, gvanrossum, rhettinger |
| Date | 2008年04月30日.06:29:53 |
| SpamBayes Score | 0.061467983 |
| Marked as misclassified | No |
| Message-id | <1209536998.92.0.675374895697.issue2719@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
IMO having next() in 2.6 helps since if you use it consistently you don't have to care about calling .next() or .__next__(). Also, I don't see how this is different from having e.g. reduce() and functools.reduce() in 2.6. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年04月30日 06:30:01 | georg.brandl | set | spambayes_score: 0.061468 -> 0.061467983 recipients: + georg.brandl, gvanrossum, rhettinger |
| 2008年04月30日 06:29:59 | georg.brandl | set | spambayes_score: 0.061468 -> 0.061468 messageid: <1209536998.92.0.675374895697.issue2719@psf.upfronthosting.co.za> |
| 2008年04月30日 06:29:57 | georg.brandl | link | issue2719 messages |
| 2008年04月30日 06:29:54 | georg.brandl | create | |