[issue7764] Doc for itertools recipe consume is complicated and less efficient

Changes by Raymond Hettinger : -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailin

[issue7764] Doc for itertools recipe consume is complicated and less efficient

Ezio Melotti added the comment: Raymond, before porting you should check the typos reported in issue #7778. -- dependencies: +Typo(s) in ``itertools`` documentation reST marker nosy: +ezio.melotti stage: needs patch -> commit review ___ Python tracke

[issue7764] Doc for itertools recipe consume is complicated and less efficient

Raymond Hettinger added the comment: No problem. Will forward port when I get a chance. -- versions: -Python 2.6 ___ Python tracker ___ _

[issue7764] Doc for itertools recipe consume is complicated and less efficient

Muhammad Alkarouri added the comment: Mea culpa. Not knowing the conventions here, I closed the ticket, which probably resulted in florent's feedback. I will leave you to it then. -- ___ Python tracker ___

[issue7764] Doc for itertools recipe consume is complicated and less efficient

Raymond Hettinger added the comment: Remain calm. I left the status as Open for a reason. When I'm satisfied that people are reacting well to the new update, will port to other versions. -- ___ Python tracker __

[issue7764] Doc for itertools recipe consume is complicated and less efficient

Florent Xicluna added the comment: Changeset r77721 should be ported to trunk, and py3k probably. -- nosy: +flox status: closed -> open ___ Python tracker ___ ___

[issue7764] Doc for itertools recipe consume is complicated and less efficient

Jan Kaliszewski added the comment: (sorry! typed into a wrong field) -- nosy: +zuo versions: +Python 2.6, Python 2.7, Python 3.2 ___ Python tracker ___ __

[issue7764] Doc for itertools recipe consume is complicated and less efficient

Changes by Jan Kaliszewski : -- title: dictview -> Doc for itertools recipe consume is complicated and less efficient ___ Python tracker ___ _

[issue7764] Doc for itertools recipe consume is complicated and less efficient

Muhammad Alkarouri added the comment: Excellent solution and comments. Many thanks. -- status: open -> closed ___ Python tracker ___ _

[issue7764] Doc for itertools recipe consume is complicated and less efficient

Raymond Hettinger added the comment: See r77721 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue7764] Doc for itertools recipe consume is complicated and less efficient

Raymond Hettinger added the comment: Will switch to the version using next() instead of deque(). -- ___ Python tracker ___ ___ Python-

[issue7764] Doc for itertools recipe consume is complicated and less efficient

Peter Otten <__pete...@web.de> added the comment: As noted on comp.lang.python the implementation can be simplified to def consume(items, n): next(islice(items, n, n), None) When I suggested the above I wasn't aware that consume(items, None) should exhaust the entire iterator. Unfortunat

[issue7764] Doc for itertools recipe consume is complicated and less efficient

Changes by Georg Brandl : -- assignee: georg.brandl -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7764] Doc for itertools recipe consume is complicated and less efficient

Changes by Ezio Melotti : -- nosy: +rhettinger priority: -> normal stage: -> needs patch versions: +Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___ ___

[issue7764] Doc for itertools recipe consume is complicated and less efficient

New submission from Muhammad Alkarouri : Based on the discussion at: http://groups.google.co.uk/group/comp.lang.python/browse_thread/thread/c1ae3513a31eb63e/d0701a9902732c67?hl=en#d0701a9902732c67 In the documentation of itertools, one of the functions provided in the recipes section (10.7.3) i