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 steven.daprano
Recipients Leon Avery, steven.daprano
Date 2017-07-24.13:50:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> This means that a user who wishes to use '--' in some other way is out of luck. 

I think that's a feature, not a limitation.

Command line arguments should use broadly consistent conventions. I don't want one program to use '--' for "end of options" and another program to use it for "something else".

Suppose you want to use '--' for "foo", and '%%' (say) as the end of options terminator. Whatever foo is. Okay, just swap them -- keep the usual convention where '--' is the options terminator, and use '%%' for foo. That way your users won't be surprised and confused by your application working differently from the great bulk of commandline applications. (Users never read the manual.)

But maybe I'll change my mind if you can show that there's already a very common, and useful, alternative convention of '--' for foo, for some definition of foo.
Date User Action Args
2017-07-24 13:50:46steven.dapranosetrecipients: + steven.daprano, Leon Avery
2017-07-24 13:50:46steven.dapranosetmessageid: <>
2017-07-24 13:50:46steven.dapranolinkissue31012 messages
2017-07-24 13:50:46steven.dapranocreate