[issue15427] Describe use of args parameter of argparse.ArgumentParser.parse_args

2017-09-09 Thread Mariatta Wijaya
Mariatta Wijaya added the comment: Thanks, David. I merged the backport PRs. Closing this. -- nosy: +Mariatta resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue15427] Describe use of args parameter of argparse.ArgumentParser.parse_args

2017-09-04 Thread R. David Murray
Changes by R. David Murray : -- pull_requests: +3350 ___ Python tracker ___ ___

[issue15427] Describe use of args parameter of argparse.ArgumentParser.parse_args

2017-09-04 Thread R. David Murray
Changes by R. David Murray : -- pull_requests: +3348 ___ Python tracker ___ ___

[issue15427] Describe use of args parameter of argparse.ArgumentParser.parse_args

2017-09-04 Thread R. David Murray
Changes by R. David Murray : -- versions: +Python 3.6, Python 3.7 -Python 3.2, Python 3.3, Python 3.4 ___ Python tracker ___

[issue15427] Describe use of args parameter of argparse.ArgumentParser.parse_args

2017-09-04 Thread R. David Murray
R. David Murray added the comment: I've turned this into a PR. The example was already changed in a previous checkin. I reworded the optparse porting addition to match the existing style of the list. -- nosy: +r.david.murray ___ Python tracker

[issue15427] Describe use of args parameter of argparse.ArgumentParser.parse_args

2017-09-04 Thread R. David Murray
Changes by R. David Murray : -- pull_requests: +3327 ___ Python tracker ___ ___

[issue15427] Describe use of args parameter of argparse.ArgumentParser.parse_args

2013-04-18 Thread Glenn Linderman
Glenn Linderman added the comment: These docs changes seem reasonable, from a side-by-side view (I didn't attempt to look at the formatted results of applying the patch), to better document the current behavior. -- nosy: +v+python ___ Python

[issue15427] Describe use of args parameter of argparse.ArgumentParser.parse_args

2013-04-03 Thread paul j3
paul j3 added the comment: This patch to argparse.rst adds the argument points to parse_args(). It also adds two points to the 'Upgrading optparse code' section, one about using 'nargs=argparse.REMAINDER', and other about 'parse_known_args()'. I'm not entirely happy with the format of the

[issue15427] Describe use of args parameter of argparse.ArgumentParser.parse_args

2013-04-03 Thread paul j3
paul j3 added the comment: I changed the reference to the optparse allow_interspersed_args attribute to the disable_interspersed_args() method. -- Added file: http://bugs.python.org/file29662/remainder.patch ___ Python tracker rep...@bugs.python.org

[issue15427] Describe use of args parameter of argparse.ArgumentParser.parse_args

2013-04-02 Thread paul j3
paul j3 added the comment: The 'args=' parameter is the same as the first positional parameter used in most of the examples. That is normal Python behavior. 15.4.4.5. Beyond sys.argv explains this alternative way of specifying argv. Still 2 bullet points could be added to 15.4.4. - args - A

[issue15427] Describe use of args parameter of argparse.ArgumentParser.parse_args

2012-07-22 Thread Steven Bethard
New submission from Steven Bethard steven.beth...@gmail.com: From http://bugs.python.org/issue14191#msg155202: ArgumentParser.parse_args(args=None, namespace=None) ... However, nowhere is the args= parameter explained. One example is given at the end of 15.4.4.6 showing the use of args= which