[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Andrew Svetlov added the comment: Fixed in 4712f9f8a90d, 5e5081cdc086, e4beda7cca2f. Thanks. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker _

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Kostyantyn Leschenko added the comment: I've updated patch to work with current trunk. -- nosy: +Kostyantyn.Leschenko, asvetlov versions: +Python 3.4 -Python 3.2 Added file: http://bugs.python.org/file29704/Issue13249-5.patch ___ Python tracker

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Mark Lawrence added the comment: Can someone please review the latest patch and commit if appropriate. -- nosy: +BreamoreBoy ___ Python tracker ___ __

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Steven Bethard added the comment: I've updated the patch for the current trunk. Should be ready to commit. -- Added file: http://bugs.python.org/file26490/Issue13249-4.patch ___ Python tracker

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Steven Bethard added the comment: The ArgumentParser constructor is definitely only intended to be called with keyword arguments, so it's definitely a documentation bug that it doesn't say this. I haven't actually applied the patch, but the basic approach and wording look fine to me. ---

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Roy Smith added the comment: Another patch, with the most recent review suggestions incorporated. -- Added file: http://bugs.python.org/file23703/Issue13249-3.patch ___ Python tracker _

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Terry J. Reedy added the comment: I agree with Eric both as to placement (first paragraph) and wording (with explanation). I don't have time to review otherwise at the moment. -- ___ Python tracker __

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Roy Smith added the comment: Before I build another patch, would you be OK with leaving it as a note, but adding the "due to the number of arguments" language? There's a lot of text here, and people tend to just zoom in on the bits and pieces they need right now. I think there is value in m

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Éric Araujo added the comment: I would not use a note directive. Notes and warnings distract and sometimes scare readers. For a simple coding recommendation like this, I think a regular paragraph would suffice. To make sure it’s not lost after pages of options description, maybe it could b

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Roy Smith added the comment: New patch uploaded. The added recommendation is around line 161 (look for 'Recommended usage is to only use keyword arguments') -- Added file: http://bugs.python.org/file23667/Issue13249-2.patch ___ Python tracker

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Éric Araujo added the comment: Thanks, I’ve made some comments on Rietveld. > Added a recommendation to only use keywords, which seems sane given > the number of arguments. I looked for that but couldn’t find it. -- nosy: +eric.araujo ___ Python tra

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Roy Smith added the comment: PS -- this is against the 2.7 branch. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Roy Smith added the comment: Patch attached. I just deal with putting all the items into the same order, not terry.reedy's idea for separating them into two groups. Added a recommendation to only use keywords, which seems sane given the number of arguments. -- keywords: +patch Added

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Roy Smith added the comment: I'm working on a doc patch now... -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Roy Smith added the comment: An Nth place is in the docstring: Keyword Arguments: - prog -- The name of the program (default: sys.argv[0]) - usage -- A usage m

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Terry J. Reedy added the comment: In the doc, the signature line is followed by a list of short descriptions in a third order. That perhaps should be changed to follow the same corrected order as the signature line. On the other hand, it matches the order of the detail sections that follow. O

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Changes by Santoso Wijaya : -- nosy: +santa4nt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Petri Lehtinen added the comment: Fixing the documentation is better, as changing the argument order would break existing code. -- keywords: +easy nosy: +petri.lehtinen ___ Python tracker

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

Florent Xicluna added the comment: in 3.x, same issue. IMHO documentation should be fixed. -- assignee: -> docs@python components: +Documentation nosy: +bethard, docs@python, flox stage: -> needs patch versions: +Python 3.2, Python 3.3 ___ Python t

[issue13249] argparse.ArgumentParser() lists arguments in the wrong order

New submission from Roy Smith : The docs list the arguments in the order: class argparse.ArgumentParser([description][, epilog][, prog]... but the code (I'm looking at the 2.7.2 source) lists them as: class ArgumentParser(_AttributeHolder, _ActionsContainer): [...] def __init__(self,