[issue11908] Weird `slice.stop or sys.maxint`

2013-07-11 Thread Raymond Hettinger
Raymond Hettinger added the comment: Closing for the reasons lists above. -- resolution: -> rejected status: open -> closed ___ Python tracker ___ __

[issue11908] Weird `slice.stop or sys.maxint`

2013-07-07 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- versions: -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue11908] Weird `slice.stop or sys.maxint`

2012-12-27 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- stage: commit review -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue11908] Weird `slice.stop or sys.maxint`

2012-12-02 Thread Raymond Hettinger
Raymond Hettinger added the comment: ysj: The "equivalent" means "roughly equivalent" not "precisely equivalent". The purpose of the code in the docs is to help communicate what islice() is all about. Practicality beats purity in this regard. I know of no one who has ever been mislead by t

[issue11908] Weird `slice.stop or sys.maxint`

2012-12-02 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- priority: normal -> low ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue11908] Weird `slice.stop or sys.maxint`

2012-12-02 Thread Mark Dickinson
Changes by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue11908] Weird `slice.stop or sys.maxint`

2012-12-01 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: LGTM. However note, that for 2.7 the patch should be modified (maxsize -> maxint, range -> xrange). -- nosy: +serhiy.storchaka stage: needs patch -> commit review versions: +Python 3.4 ___ Python tracker

[issue11908] Weird `slice.stop or sys.maxint`

2012-07-07 Thread Brian Brazil
Brian Brazil added the comment: The attached patch fixes this -- keywords: +patch nosy: +bbrazil Added file: http://bugs.python.org/file26283/issue11908-islice-docs.patch ___ Python tracker ___

[issue11908] Weird `slice.stop or sys.maxint`

2011-11-19 Thread Ezio Melotti
Changes by Ezio Melotti : -- keywords: +easy nosy: +ezio.melotti stage: -> needs patch versions: -Python 3.1 ___ Python tracker ___

[issue11908] Weird `slice.stop or sys.maxint`

2011-04-25 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- versions: -Python 2.5, Python 2.6, Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue11908] Weird `slice.stop or sys.maxint`

2011-04-25 Thread Raymond Hettinger
Raymond Hettinger added the comment: I've got from here. Thanks. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue11908] Weird `slice.stop or sys.maxint`

2011-04-25 Thread ysj.ray
ysj.ray added the comment: `step` argument for xrange() could not be 0. But `s.stop or sys.maxint` is really a problem, in the case of `s.stop == 0`. So the given `Equivalent to` python code in the doc is not precisely equivalent to the c implementation. The doc needs a fix. -- nosy:

[issue11908] Weird `slice.stop or sys.maxint`

2011-04-22 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- assignee: docs@python -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list ma

[issue11908] Weird `slice.stop or sys.maxint`

2011-04-22 Thread Ram Rachum
New submission from Ram Rachum : In the documentation for `itertools.islice` I see this line: it = iter(xrange(s.start or 0, s.stop or sys.maxint, s.step or 1)) Is it really okay to do `s.stop or sys.maxint`? I'm assuming this was targeting `None`, but what if `s.stop == 0`? And `s.step` c