Ned Deily <n...@python.org> added the comment:
That's an interesting question. There is much prior art here dating back to the earliest days of Unix. The Open Group Base Specification has a section dealing with the syntax of utility arguments with suggestions of when or when not a space between the option and the option argument is needed and how to document the difference, i.e. [-c option_argument] vs [-f[option_argument]] https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html#tag_12_01 It looks like the Python man page already sort of uses this syntax but the Python Setup and Usage doc may have different conventions. If someone wants to pursue this, they might check all the options and provide a PR with any needed updates to the man page and the doc page. A change in behavior of the command option processing is probably not a good idea at this point unless there is some demonstrable error or ambiguity. ---------- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python, ned.deily versions: -Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue38690> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
