[issue6372] Make all switches keyword-only

Pablo Torres Navarrete added the comment: OK, bad idea it is then. Thank you for your time. -- ___ Python tracker ___ ___ Python-bugs

[issue6372] Make all switches keyword-only

Martin v. Löwis added the comment: Just to add another voice: I would be opposed if such breakage is added before Python 4. -- nosy: +loewis ___ Python tracker ___ __

[issue6372] Make all switches keyword-only

Raymond Hettinger added the comment: Let me get this right, you don't like it when people use positional arguments for options and switches. So, you want to force them to change to a style you do like by breaking their existing code. And once they've changed, their code will be slower, more ve

[issue6372] Make all switches keyword-only

Georg Brandl added the comment: Closing this for now; it really needs some serious discussion so a tracker item is not appropriate. -- nosy: +georg.brandl resolution: -> wont fix status: open -> closed ___ Python tracker

[issue6372] Make all switches keyword-only

R. David Murray added the comment: I suspect it would require a PEP, since it would mean breaking backward compatibility in a rather extensive fashion. I suggest floating this idea on python-ideas first for feedback. -- nosy: +r.david.murray ___ Pyt

[issue6372] Make all switches keyword-only

New submission from Pablo Torres Navarrete : I propose that all formal parameters that really act as options/switches be made keyword-only. Examples of switches are all flags, timeouts, 'verbose' bools, maximums and minimums, etc. This stresses the difference between needed input for a function