README
1 This repository contains a python implementation of the Google commandline
2 flags module.
3
4 GFlags defines a *distributed* command line system, replacing systems like
5 getopt(), optparse and manual argument processing. Rather than an application
6 having to define all flags in or near main(), each python module defines flags
7 that are useful to it. When one python module imports another, it gains
8 access to the other's flags.
9
10 It includes the ability to define flag types (boolean, float, interger, list),
11 autogeneration of help (in both human and machine readable format) and reading
12 arguments from a file. It also includes the ability to automatically generate
13 man pages from the help flags.
14
15 Documentation for implementation is at the top of gflags.py file.
16
17 To install the python module, run
18 python ./setup.py install
19
20 When you install this library, you also get a helper application,
21 gflags2man.py, installed into /usr/local/bin. You can run gflags2man.py to
22 create an instant man page, with all the commandline flags and their docs, for
23 any C++ or python program you've written using the gflags library.
24
README.chromium
1 Name: python-gflags
2 URL: http://code.google.com/p/python-gflags/
3 Version: 2.0
4 Date: 15 Feb 2012
5 Revision: 41
6 License: BSD 3-Clause License
7 License File: NOT_SHIPPED
8 Security Critical: no
9
10 Description:
11 This project is the python equivalent of google-gflags, a Google commandline
12 flag implementation for C++. It is intended to be used in situations where a
13 project wants to mimic the command-line flag handling of a C++ app that uses
14 google-gflags, or for a Python app that, via swig or some other means, is
15 linked with a C++ app that uses google-gflags.
16
17 The gflags package contains a library that implements commandline flags
18 processing. As such it's a replacement for getopt(). It has increased
19 flexibility, including built-in support for Python types, and the ability to
20 define flags in the source file in which they're used. (This last is its
21 major difference from OptParse.)
22
23 Local modifications:
24 Removed tests/
25 Removed debian/
26 Added OWNERS file
27