[issue8706] accept keyword arguments on most base type methods and builtins

INADA Naoki added the comment: TL;DR Changing positional argument name doesn't break backward compatibility. After start accepting keyword argument, it's name is part of API and should be stable. For example, document says `str.startswith(prefix[, start[, end]])`. But this patch seems using

[issue8706] accept keyword arguments on most base type methods and builtins

Serhiy Storchaka added the comment: Most overhead of supporting keyword arguments when pass positional arguments was removed in issue29029. But still there is an overhead of passing argument by keywords. It can be decreased when convert functions to Argument Clinic or use new private argument

[issue8706] accept keyword arguments on most base type methods and builtins

Changes by Nicholas Chammas : -- nosy: +Nicholas Chammas ___ Python tracker ___

[issue8706] accept keyword arguments on most base type methods and builtins

Gregory P. Smith added the comment: I wouldn't make an efficiency argument against it without trying it and showing reproducible degradation in the hg.python.org/benchmarks suite. On Sun, Apr 19, 2015, 10:31 PM Serhiy Storchaka rep...@bugs.python.org wrote: Serhiy Storchaka added the

[issue8706] accept keyword arguments on most base type methods and builtins

Changes by Berker Peksag berker.pek...@gmail.com: -- components: +Extension Modules, Interpreter Core nosy: +berker.peksag versions: +Python 3.5 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8706

[issue8706] accept keyword arguments on most base type methods and builtins

Martin Panter added the comment: See also Issue 23738, which identifies some functions whose documentation already suggests they accept keywords. Perhaps these functions could be prioritized. Also, I think “version changed” notices should be added in the documentation when a function grows

[issue8706] accept keyword arguments on most base type methods and builtins

Serhiy Storchaka added the comment: Supporting keyword arguments has performance loss. For fast builtins it make be significant. We should defer adding keyword arguments support until more efficient parsing will implemented. Note that it is easier to implement efficient argument parsing for

[issue8706] accept keyword arguments on most base type methods and builtins

Julien Palard added the comment: I think for some builtins it may be usefull to have keyword arguments, in the case they take more than one parameter. Typically, it's impossible to write: self.drop_elements(partial(isinstance, type(lxml.etree.Comment))) Because isinstance take its

[issue8706] accept keyword arguments on most base type methods and builtins

Éric Araujo mer...@netwok.org added the comment: See also #13386 for the doc part. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8706 ___ ___

[issue8706] accept keyword arguments on most base type methods and builtins

Éric Araujo mer...@netwok.org added the comment: I agree with Ezio and Raymond. Tentatively editing the title to reflect the reduction in scope. -- nosy: +eric.araujo title: accept keyword arguments on all base type methods and builtins - accept keyword arguments on most base type

[issue8706] accept keyword arguments on most base type methods and builtins

Gregory P. Smith g...@krypto.org added the comment: restricting the scope of this makes sense. also: just because an argument is listed in the docs with a name does not mean that that name is the most appropriate; part of adding keyword support should be choosing a sensible name. Keyword

[issue8706] accept keyword arguments on most base type methods and builtins

Ezio Melotti ezio.melo...@gmail.com added the comment: also: just because an argument is listed in the docs with a name does not mean that that name is the most appropriate; part of adding keyword support should be choosing a sensible name. I agree, but other implementations might not

[issue8706] accept keyword arguments on most base type methods and builtins

Gregory P. Smith g...@krypto.org added the comment: I kicked off a discussion on python-ideas. Lets take this there for the time being. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8706