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 Arfrever, Ramchandra Apte, brian.curtin, eric.snow, ezio.melotti, gregory.p.smith, gruszczy, meatballhat, rhettinger
Date 2012-02-28.05:16:05
SpamBayes Score 1.9475746e-07
Marked as misclassified No
Message-id <1330406166.3.0.404070094989.issue8706@psf.upfronthosting.co.za>
In-reply-to
Content
range() has been around 20+ years and there has been zero need for keyword arguments for it.

FWIW, the maxsplit keyword argument was a case where a keyword argument added clarity, and there may be a handful of other cases that are also warranted.  Greg Smith's idea for "start" for str.find() may be one of those.   

People are welcome to propose individual suggestions in separate tracker items; however, if someone wants a wholesale set of changes to core builtins, then they should discuss it on python-ideas.  It would also be worthwhile for someone to benchmark the performance cost of switching from "METH_O" to "METH_VARARGS | METH_KEYWORDS".
History
Date User Action Args
2012-02-28 05:16:06rhettingersetrecipients: + rhettinger, gregory.p.smith, ezio.melotti, Arfrever, brian.curtin, gruszczy, meatballhat, eric.snow, Ramchandra Apte
2012-02-28 05:16:06rhettingersetmessageid: <1330406166.3.0.404070094989.issue8706@psf.upfronthosting.co.za>
2012-02-28 05:16:05rhettingerlinkissue8706 messages
2012-02-28 05:16:05rhettingercreate