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 | eopadoan |
|---|---|
| Recipients | eopadoan |
| Date | 2007年09月15日.15:19:46 |
| SpamBayes Score | 0.020213878 |
| Marked as misclassified | No |
| Message-id | <1189869587.07.0.169329623403.issue1165@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Currently, itertools.count.__next__ checks wether the current value is > PY_SSIZE_T_MAX and raises OverflowError if so. Shouldn't the value be stored as "long", at least in Py3k? Not that I have any use case for it, so it is minor. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年09月15日 15:19:47 | eopadoan | set | spambayes_score: 0.0202139 -> 0.020213878 recipients: + eopadoan |
| 2007年09月15日 15:19:47 | eopadoan | set | spambayes_score: 0.0202139 -> 0.0202139 messageid: <1189869587.07.0.169329623403.issue1165@psf.upfronthosting.co.za> |
| 2007年09月15日 15:19:46 | eopadoan | link | issue1165 messages |
| 2007年09月15日 15:19:46 | eopadoan | create | |