[issue16678] optparse: parse only known options

2012-12-14 Thread R. David Murray
Changes by R. David Murray : -- resolution: -> out of date stage: -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue16678] optparse: parse only known options

2012-12-14 Thread Andrew Svetlov
Andrew Svetlov added the comment: +1 for closing as "won't fix" -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing

[issue16678] optparse: parse only known options

2012-12-14 Thread Éric Araujo
Éric Araujo added the comment: I agree with David and suggest closing this as outdated. Thanks for the suggestion nonetheless. -- nosy: +eric.araujo ___ Python tracker ___

[issue16678] optparse: parse only known options

2012-12-14 Thread R. David Murray
R. David Murray added the comment: We aren't encouraging people to use optparse any more. The recipe isn't needed in argparse, as that has a "parse_known_args" method that achieves the same end. -- nosy: +r.david.murray ___ Python tracker

[issue16678] optparse: parse only known options

2012-12-14 Thread anatoly techtonik
anatoly techtonik added the comment: It allows to port options to and from optparse incrementally. -- ___ Python tracker ___ ___ Pytho

[issue16678] optparse: parse only known options

2012-12-14 Thread anatoly techtonik
Changes by anatoly techtonik : Added file: http://bugs.python.org/file28307/pass_through.py ___ Python tracker ___ ___ Python-bugs-list mailin

[issue16678] optparse: parse only known options

2012-12-14 Thread anatoly techtonik
New submission from anatoly techtonik: This following recipe from Optik examples should be added to documentation. It is extremely helpful when porting to optparse from getopt or other option parsing schemes. -- assignee: docs@python components: Documentation messages: 177447 nosy: doc