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 baptiste.carvello
Recipients baptiste.carvello, docs@python, eli.bendersky, eric.araujo, eric.smith, eric.snow, ezio.melotti, georg.brandl, petri.lehtinen, terry.reedy
Date 2011-11-18.07:11:42
SpamBayes Score 4.554808e-07
Marked as misclassified No
Message-id <4EC60527.5080409@baptiste-carvello.net>
In-reply-to <1321590572.06.0.541036897626.issue13386@psf.upfronthosting.co.za>
Content
Le 18/11/2011 05:29, Terry J. Reedy a écrit :
> 
> In the following, I give objections to this PO (position only) rule and suggest an alternative ND (no default) rule: use 'name=default' when there is a default and '[name]' when there is not'.
> 
> The issue of whether an argument is required or optional is orthogonal to whether it can be passed by both position and name, only by name, or only by position.

With this logic, you would need to use '[name=default]' when an argument
is optional *and* can be passed by name.

Sure, this notation is inherently redundant, but is has the advantage of
conveying both informations immediately to the user. It is also more
coherent with '[name]'.

But this is a big change from the current philosophy...
History
Date User Action Args
2011-11-18 07:11:43baptiste.carvellosetrecipients: + baptiste.carvello, georg.brandl, terry.reedy, eric.smith, ezio.melotti, eric.araujo, eli.bendersky, docs@python, eric.snow, petri.lehtinen
2011-11-18 07:11:42baptiste.carvellolinkissue13386 messages
2011-11-18 07:11:42baptiste.carvellocreate