Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - patch review
versions: -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8706
___
Gregory P. Smith g...@krypto.org added the comment:
At a quick glance, I think you've got the right idea. Fixing this involves a
lot of PyArg_ParseTuple - PyArg_ParseTupleAndKeywords upgrades all over the
place.
Obviously there are are a wide range of things that can use updating for this
Filip Gruszczyński grusz...@gmail.com added the comment:
Do you think I should put everything into a single patch or rather slowly add
new patches with different methods or method groups?
I would rather split it into several patches, I think it is easier to manage
them, especially that this
Gregory P. Smith g...@krypto.org added the comment:
Several patches for sure! and give the patch files useful names
indicating which things they touch.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8706
Ezio Melotti ezio.melo...@gmail.com added the comment:
On one hand I agree that it would be nice to get rid of these implementation
details that prevent some C functions/methods to accept keyword args, but on
the other hand I'm not sure that changing them all is the right thing to do.
For some
Brian Curtin br...@python.org added the comment:
For some functions/methods being able to pass keyword args make the code more
readable/flexible, but for some other there's no real gain.
I know what you're saying with the last part, but I think everyone becomes a
winner in the consistency
Ezio Melotti ezio.melo...@gmail.com added the comment:
FWIW PyPy doesn't seem to support keyword args for e.g. str.join() (so that's
extra work for them too), and I don't see what would be the advantage of being
able to do '-'.join(iterable=a_list). Even if I also don't see a valid reason
Filip Gruszczyński grusz...@gmail.com added the comment:
I would stay away from methods that accept just a single argument. For those
that accept more, I think it's reasonable to allow keyword args.
--
___
Python tracker rep...@bugs.python.org
Changes by Eric Snow ericsnowcurren...@gmail.com:
--
nosy: +eric.snow
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8706
___
___
Python-bugs-list
Raymond Hettinger raymond.hettin...@gmail.com added the comment:
For many builtins, this would be a total waste, slowing down the calls, and
supplying keyword names that would be meaningless or just weird. For example,
chr(i=65) is just a waste.
Keyword args should only be added where they
Ramchandra Apte maniandra...@gmail.com added the comment:
See also issue14081 which got fixed.
--
nosy: +ramchandra.apte
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8706
___
Ramchandra Apte maniandra...@gmail.com added the comment:
Can we have keyword arguments to range([start],stop,[step])?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8706
___
Raymond Hettinger raymond.hettin...@gmail.com added the comment:
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
Filip Gruszczyński grusz...@gmail.com added the comment:
I don't know if this is exactly what you want, but this is an early patch.
--
keywords: +patch
nosy: +gruszczy
Added file: http://bugs.python.org/file24644/8706.patch
___
Python tracker
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8706
___
Filip Gruszczyński grusz...@gmail.com added the comment:
With tests.
--
Added file: http://bugs.python.org/file24650/8706_2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8706
___
New submission from Gregory P. Smith g...@krypto.org:
C Python has a real wart in that standard types and library functions that are
implemented in C do not always accept keyword arguments:
'xx'.find('xx', 4)
4
'xx'.find('xx', start=4)
Traceback (most recent call last):
File stdin,
Changes by Dan Buch daniel.b...@gmail.com:
--
nosy: +meatballhat
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8706
___
___
Python-bugs-list
18 matches
Mail list logo
