[issue5555] optparse: clarify option concatenation in docs

Aaron Sherman added the comment: I'm closing this out, as the previous poster was correct: the module does the right thing, and I misread the documentation. Thanks! -- status: open -> closed ___ Python tracker

[issue5555] optparse: clarify option concatenation in docs

Changes by Greg Ward : -- title: optparse -> optparse: clarify option concatenation in docs ___ Python tracker ___ ___ Python-bugs-list

[issue5555] optparse

Greg Ward added the comment: > This is an edited-down excerpt form the optparse documentation from: > > http://docs.python.org/library/optparse.html > > "... the traditional Unix syntax is a hyphen (“-“) followed by a > single letter [...] Some other option syntaxes that the world has seen in

[issue5555] optparse

Changes by Ezio Melotti : -- nosy: +gward priority: -> low ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue5555] optparse

New submission from Aaron Sherman : First off, I want to be clear that this isn't a request for changes to functionality, nor for debate over decisions which have already been made. This is purely a request for correction to mis-statements about the nature and origins of optparse's handling in it