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 lehmannro
Recipients Ramchandra Apte, dair-targ, lehmannro
Date 2012-05-30.09:11:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1338369061.52.0.842779538963.issue14961@psf.upfronthosting.co.za>
In-reply-to
Content
Your proposal seems two-fold: (a) make map/filter lazy and (b) have them as methods instead of functions.

It seems Tim borrowed Guido's time machine and already implemented (a) in Python 3.x, see http://docs.python.org/py3k/library/functions.html#map and http://docs.python.org/py3k/library/functions.html#filter.

Your second proposal-- which is better suited for python-ideas, really --is obstructed by iterators being merely a protocol (the next/__next__ method) which makes it hard to add those methods to one particular type. (This very discussion pops up every so often for str.join too.)

I'd recommend closing this issue.
History
Date User Action Args
2012-05-30 09:11:01lehmannrosetrecipients: + lehmannro, Ramchandra Apte, dair-targ
2012-05-30 09:11:01lehmannrosetmessageid: <1338369061.52.0.842779538963.issue14961@psf.upfronthosting.co.za>
2012-05-30 09:11:00lehmannrolinkissue14961 messages
2012-05-30 09:11:00lehmannrocreate