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 Matt Gilson, mgilson, rhettinger, serhiy.storchaka
Date 2017-05-12.19:38:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494617906.53.0.122482854803.issue30346@psf.upfronthosting.co.za>
In-reply-to
Content
I have no interest in #2.   Itertools are all about *not* storing data in memory unless that is an intrinsic requirement for the operation (tee() and cycle() for example).

Also, I would like any changes to be minimal and have the lowest possible risk of breaking code.  The groupby() tool is about 13 years old and has served its users well.  These little corner cases we're working on now don't seem to correspond to how users actually use groupby or how it was intended to be used (either eat the sub-iterator right away before advancing the outer iterator or ignore it entirely).
History
Date User Action Args
2017-05-12 19:38:26rhettingersetrecipients: + rhettinger, serhiy.storchaka, mgilson, Matt Gilson
2017-05-12 19:38:26rhettingersetmessageid: <1494617906.53.0.122482854803.issue30346@psf.upfronthosting.co.za>
2017-05-12 19:38:26rhettingerlinkissue30346 messages
2017-05-12 19:38:26rhettingercreate