byte compile files, etc.

       dh_python2 -p PACKAGE [-V [X.Y][-][A.B]] DIR_OR_FILE [-X REGEXPR]

       o if necessary, describe supported Python versions via X-Python-Version
         field in debian/control,

       o build-depend on python or python-all or python-all-dev (>= 2.6.6-3~),

       o build module/application using its standard build system, remember to
         build extensions for all supported Python versions (loop over  pyver-
         sions -vr),

       o install  files to the standard locations, add --install-layout=deb to
         setup.py's install command if your package is using distutils,

       o add python2 to dh's --with option, or:

       o include /usr/share/cdbs/1/class/python-distutils.mk  in  debian/rules
         and depend on cdbs (>= 0.4.90), or:

       o call dh_python2 in the binary-* target,

       o add ${python:Depends} to Depends,

       In  order  to  support  more than one Python version in the same binary
       package, dh_python2 (unlike dh_pycentral and dh_pysupport) creates sym-
       links  to  all supported Python versions at build time. It means binNMU
       (or sourceful upload in case of architecture independent  packages)  is
       required  once  a  list  of  supported  Python version is changed. It's
       faster and more robust than its competitors, though.

       dh_python2 tries to translate  Python  dependencies  from  requires.txt
       file to Debian dependencies, use debian/pydist-overrides or --no-guess-
       ing-deps option to override it. If you want dh_python2 to generate more
       strict    dependencies    (f.e.   to   avoid   ABI   problems)   create
       debian/python-foo.pydist                   file.                    See
       /usr/share/doc/python-doc/README.PyDist  (provided  by python-doc pack-
       age) for more information.

   namespace feature
       dh_python2 parses Egg's namespace_packages.txt files  (in  addition  to
       --namespace command line argument(s)) and drops empty __init__.py files
       from binary package. pycompile will regenerates them  at  install  time
       and  pyclean  will  remove them at uninstall time (if they're no longer
       used in  installed  packages).  It's  still  a  good  idea  to  provide
       __init__.py  file in one of binary packages (even if all other packages
       use this feature).

       Files listed in debian/pkg.pyinstall file will be installed  as  public
       modules  for  all  requested  Python  versions (dh_install doesn't know
       about python's site- vs. dist-packages issue).

       Syntax: "path/to/file [VERSION_RANGE] [NAMESPACE]". debian directory is
       automatically  removed  from  the  path, so you can place your files in
       debian/ directory and install them from this location (if you  want  to
       install them in "debian" namespace, set NAMESPACE to debian). If NAMES-
       PACE is set, all listed  files  will  be  installed  in  .../dist-pack-
       ages/NAMESPACE/ directory.


       o foo.py  (installs  .../dist-packages/foo.py  for all supported Python

       o foo/bar.py 2.6- (installs .../dist-packages/foo/bar.py  for  versions
         >= 2.6)

       o foo/bar.py spam (installs .../dist-packages/spam/bar.py)

       o debian/*.py    spam.egg    2.5   (installs   .../python2.5/site-pack-
         ages/spam/egg/*.py files)

   pyremove files
       If you want to remove some files installed by build  system  (from  all
       supported Python versions or only from a subset of these versions), add
       them to debian/pkg.pyremove file.


       o *.pth (removes .pth files from .../dist-packages/)

       o bar/baz.py 2.5 (removes .../python2.5/site-packages/bar/baz.py)

              show program's version number and exit

       -h, --help
              show help message and exit

              disable guessing other supported Python versions

              disable guessing dependencies

              do not remove any files from debug packages

              don't check private directories

       -p PACKAGE, --package=PACKAGE
              act on the package named PACKAGE

       -N NO_PACKAGE, --no-package=NO_PACKAGE
              do not act on the specified package

       -V VRANGE
              specify list of supported Python versions. See pycompile(1)  for

       -X REGEXPR, --exclude=REGEXPR
              exclude  items that match given REGEXPR. You may use this option
              multiple times to build up a list of things to exclude.

              compile all files from given private directory in postinst/rtup-
              date not just the ones provided by the package (i.e. do not pass
              the --package parameter to pycompile/pyclean)

              translate given requirements into Debian  dependencies  and  add
              them   to   ${python:Depends}.  Use  it  for  missing  items  in

              translate given requirements into Debian  dependencies  and  add
              them to ${python:Recommends}

              translate  given  requirements  into Debian dependencies and add
              them to ${python:Suggests}

              use this option (multiple time if necessary) if  namespace_pack-
              ages.txt is not complete

              ignore  Egg's namespace declaration and --namespace option. This
              option will disable removing (and recreating  at  install  time)
              empty  __init__.py  files.  Removing namespace_packages.txt from
              egg-info directory has the same effect.

              generate maintainer script that will remove byte code  generated
              by python-central helper

              do not translate shebangs into Debian dependencies

       o /usr/share/doc/python/python-policy.txt.gz

       o /usr/share/doc/python-doc/README.PyDist (python-doc package)
Man Pages Copyright Respective Owners. Site Copyright (C) 1994 - 2017 Hurricane Electric. All Rights Reserved.