A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-February/019956.html below:

[Python-Dev] RE: RFC: Option Parsing Libraries

[Python-Dev] RE: RFC: Option Parsing LibrariesGreg Ward gward@python.net
Mon, 11 Feb 2002 14:40:12 -0500
On 11 February 2002, Gerson Kurz said:
> I will get beat for this, but: can it be optionally non-case-sensitive? I
> know, I know, in time-honoured unix-tradition a commandline should be
> dangerous and unforgiving in use, but still, please?

Interesting idea; should be trivial given a case-insensitive dictionary.
And hasn't such a beast been bandied about as an example of subclassing
built-in types with Python 2.2?

Anyways, that's an Optik feature requests, and belongs on
optik-users@lists.sourceforge.net.  If you're serious, take it up there.

> Also, I've just scanned the specs and didn't find some
> "rest-of-the-commandline-whatever-that-is" option. As in:
> 
> filename options file1 file2 ... filen

When you do this:

  parser = OptionParser(...)
  (options, args) = parser.parse_args()

then args is the list of positional arguments left over after parsing
options.

But again, that's a question about Optik, and belongs (for now) on the
optik-users list.

        Greg
-- 
Greg Ward - just another Python hacker                  gward@python.net
http://starship.python.net/~gward/
Paranoia is simply an optimistic outlook on life.



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4