python-coverage(1) [debian man page]

PYTHON-COVERAGE(1)					      General Commands Manual						PYTHON-COVERAGE(1)

NAME

       python-coverage - measure code coverage of Python program execution

SYNOPSIS

       python-coverage -x module.py [ARG...]
       python-coverage -e
       python-coverage -r [-m]
       python-coverage -a [file...]

DESCRIPTION

       python-coverage	executes  a Python program and measures which of its statements are executed and which are not.  It stores the information
       in the file .coverage in the current working directory.

OPTIONS

       -e     Erase the .coverage file.

       -x     Execute a Python module, giving it the remaining command line arguments.

       -r     Produce a coverage report.

       -m     With -r, show the line numbers that were missed by the execution.

       -a     Annotate source files.  For each source file foo, produce foo,cover, with executed lines prefixed by ">" and non-executed by "!".

       --help Produce a help summary.  It might be more helpful than this manual page.

AUTHOR

       The python-coverage command is a one-line Python script which calls the coverage.py Python module to do all the work.  The module was rigi-
       nally developed by Gareth Rees, and is now developed by Ned Batchelder.	The module's home page is
       http://www.nedbatchelder.com/code/modules/coverage.html.

       This manual page was cobbled together by Lars Wirzenius for Debian, by copy-pasting from the help texts from the module.

																PYTHON-COVERAGE(1)

PYTHON-CONFIG(1)					      General Commands Manual						  PYTHON-CONFIG(1)

NAME

       python-config - output build options for python C/C++ extensions or embedding

SYNOPSIS

       python-config [ --prefix ] [ --exec-prefix ] [ --includes ] [ --libs ] [ --cflags ] [ --ldflags ] [ --help ]

DESCRIPTION

       python-config helps compiling and linking programs, which embed the Python interpreter, or extension modules that can be loaded dynamically
       (at run time) into the interpreter.

OPTIONS

       --cflags
	      print the C compiler flags.

       --ldflags
	      print the flags that should be passed to the linker.

       --includes
	      similar to --cflags but only with -I options (path to python header files).

       --libs similar to --ldflags but only with -l options (used libraries).

       --prefix
	      prints the prefix (base directory) under which python can be found.

       --exec-prefix
	      print the prefix used for executable program directories (such as bin, sbin, etc).

       --help print the usage message.

EXAMPLES

       To build the singe-file c program prog against the python library, use

	      gcc $(python-config --cflags --ldflags) progr.cpp -o progr.cpp

       The same in a makefile:

	      CFLAGS+=$(shell python-config --cflags)
	      LDFLAGS+=$(shell python-config --ldflags)
	      all: progr

       To build a dynamically loadable python module, use

	      gcc $(python-config --cflags --ldflags) -shared -fPIC progr.cpp -o progr.so

SEE ALSO

       python (1)
       http://docs.python.org/extending/extending.html
       /usr/share/doc/python/faq/extending.html

AUTHORS

       This manual page was written by Johann Felix Soden <johfel@gmx.de> for the Debian project (and may be used by others).

								 November 27, 2011						  PYTHON-CONFIG(1)