Feature #8460


PATCH: optparse: add keep_unknown option

Added by felipec (Felipe Contreras) over 9 years ago. Updated over 1 year ago.

Target version:


Currently people have to do very convoluted tricks, essentially making
it impossible for optparse to keep unknown options.

The safest and cleanest way is to do it in the code itself.



Updated by zzak (Zachary Scott) over 9 years ago

  • Status changed from Open to Assigned
  • Assignee set to nobu (Nobuyoshi Nakada)

Updated by drbrain (Eric Hodel) over 9 years ago

I like this patch, I could use this feature in RDoc's option parser which ignores arguments that were valid for previous versions.

Updated by prijutme4ty (Ilya Vorontsov) over 9 years ago

Can anyone please take a look at a bug considering command-line arguments containing negative numbers (which're erroneously treated ass options) and my patch for it.
I'm afraid that keeping unknown options will silently treat negative numbers (not an exception is raised) and possibly lose their ordering. So please before accepting unknown options patch, decide which behavior for such a case is right and make a specification about negative numbers in command line(as an example, they may became non-options and in such a case this proposal will work differently).
In my bug report and a patch I proposed some specs for optparse behavior in this case, but they weren't yet accepted or declined.

Updated by felipec (Felipe Contreras) over 9 years ago

Any update on this?

Updated by felipec (Felipe Contreras) over 1 year ago

Nobody had requested any tests. It would have been much easier if 7 years ago you had written the two lines of code required to test this.

Anyway, I've rebased my changes on top of the latest master, and added some tests.

Actions #7

Updated by hsbt (Hiroshi SHIBATA) over 1 year ago

  • File deleted (delete.patch)

Also available in: Atom PDF