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 Yury.Selivanov, brett.cannon, georg.brandl, jkloth, larry, loewis, rhettinger, serhiy.storchaka, taleinat, vajrasky, zach.ware
Date 2014-08-01.02:05:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1406858752.37.0.736567045391.issue20341@psf.upfronthosting.co.za>
In-reply-to
Content
Larry, ISTM that you are bulldozing your way through something that isn't an actual problem to be solved.

>  I can see why you'd think this was a waste of time.

I don't think it is just a waste of time;  I think it is a bad idea.  You have a very strong notion of how function signatures should look (i.e. the number of arguments being irrelevant) and you want to impose your ideas on existing, stable APIs for zero benefit.   

> I view giving all builtins in Python valid signatures
> as a worthwhile goal unto itself.

I can already model the behavior of repeat() using *args and **kwds, just like I can for int(), list.pop(), range(), and slice().

You don't seem to get that those tools already work, that people understand them, that they've been stable for a long time, and that they don't need to change for any reason other than that you've worked yourself into a snit about it.
History
Date User Action Args
2014-08-01 02:05:52rhettingersetrecipients: + rhettinger, loewis, brett.cannon, georg.brandl, taleinat, larry, jkloth, Yury.Selivanov, zach.ware, serhiy.storchaka, vajrasky
2014-08-01 02:05:52rhettingersetmessageid: <1406858752.37.0.736567045391.issue20341@psf.upfronthosting.co.za>
2014-08-01 02:05:52rhettingerlinkissue20341 messages
2014-08-01 02:05:51rhettingercreate