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 AlokSinghal, loewis, rhettinger, terry.reedy, thomasguest
Date 2014-06-22.08:50:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403427058.5.0.506849147649.issue6305@psf.upfronthosting.co.za>
In-reply-to
Content
Martin, "finding it sad" doesn't really help much here.

We *can* put the patch in.  Alok devoted a good chunk of time to creating the patch and I've already devoted a good chunk of time to reviewing it.  

However, in so doing I became concerned that it wasn't the right thing to do.  The code size and complexity is much bigger than I expected (as compared to what I had to do for itertools.count for example).  The use case is much weaker (because unlike range() and count() we don't have an arbitrary start point).  This thought surfaced when reading Alok's notes on the difficulty of testing this patch in a reasonable amount of time.

Besides feeling sad, what is your recommendation?  Would you like me to finish the review and check it in to make everyone feel good?
History
Date User Action Args
2014-06-22 08:50:58rhettingersetrecipients: + rhettinger, loewis, terry.reedy, thomasguest, AlokSinghal
2014-06-22 08:50:58rhettingersetmessageid: <1403427058.5.0.506849147649.issue6305@psf.upfronthosting.co.za>
2014-06-22 08:50:58rhettingerlinkissue6305 messages
2014-06-22 08:50:58rhettingercreate