dh-python provides various tools that help packaging Python related files
in Debian.
pybuildis a tool that implementsdhsequencer'sdh_auto_foocommands (but it can be used outsidedhas well). It builds and installs files.dh_python3is a tool that takes whatpybuildproduces and generates runtime dependencies and maintainer scripts. It fixes some common mistakes, like installing files intosite-packagesinstead ofdist-packages,/usr/local/bin/shebangs, removes.pyfiles from-dbgpackages, etc.)To translate
requires.txt(a file installed indist-packages/foo.egg-info/) into Debian dependencies, a list of packages that provide given egg distribution is used. If the dependency is not found there,dpkg -Sis used (i.e. a given dependency has to be installed; you need it inBuild-Dependsin order to run tests anyway). See dependencies section indh_python3's manpage for more details.dh_python3works on./debian/python3-foo/files and other binary packages that have${python3:Depends}in theDependsfield. Seedh_python3manpage for more details.
A simplified work flow looks like this:
# dh_auto_clean stage
for interpreter in REQUESTED_INTERPRETERS:
for version in interpreter.REQUESTED_VERSIONS:
PYBUILD_BEFORE_CLEAN
pybuild --clean
PYBUILD_AFTER_CLEAN
plenty_of_other_dh_foo_tools_invoked_here
# dh_auto_configure stage
for interpreter in REQUESTED_INTERPRETERS:
for version in interpreter.REQUESTED_VERSIONS:
PYBUILD_BEFORE_CONFIGURE
pybuild --configure
PYBUILD_AFTER_CONFIGURE
plenty_of_other_dh_foo_tools_invoked_here
# dh_auto_build stage
for interpreter in REQUESTED_INTERPRETERS:
for version in interpreter.REQUESTED_VERSIONS:
PYBUILD_BEFORE_BUILD
pybuild --build
PYBUILD_AFTER_BUILD
plenty_of_other_dh_foo_tools_invoked_here
# dh_auto_test stage
for interpreter in REQUESTED_INTERPRETERS:
for version in interpreter.REQUESTED_VERSIONS:
PYBUILD_BEFORE_TEST
pybuild --test
PYBUILD_AFTER_TEST
plenty_of_other_dh_foo_tools_invoked_here
# dh_auto_install stage
for interpreter in REQUESTED_INTERPRETERS:
for version in interpreter.REQUESTED_VERSIONS:
PYBUILD_BEFORE_INSTALL
pybuild --install
PYBUILD_AFTER_INSTALL
plenty_of_other_dh_foo_tools_invoked_here
dh_python3
plenty_of_other_dh_foo_tools_invoked_hereThis command is auto-detected, it currently supports distutils, autotools,
cmake and a custom build system where you can define your own set of
commands. Why do we need it? dh_auto_foo doesn't know each command has to
be invoked for each interpreter and version.
is parsed from Build-Depends if --buildsystem=pybuild is set. If it's
not, you have to pass --interpreter to pybuild (more in its manpage)
python3-all{,-dev}- all CPython interpreters (for packages that provide public modules / extensions)python3-all-dbg- all CPython debug interpreters (if-dbgpackage is provided)python3- default CPython or closest to default interpreter only (use this if you build a Python application)python3-dbg- default CPython debug (or closest to the default one) only
is parsed from X-Python3-Version and Build-Depends.
can be different for each interpreter and/or version, examples:
PYBUILD_AFTER_BUILD_python3.5=rm {destdir}/{build_dir}/foo/bar2X.pyPYBUILD_BEFORE_INSTALL_python3=touch {destdir}/{install_dir}/foo/bar/__init__.py
These commands should be used only if overriding dh_auto_foo is not enough
(example below)
override_dh_auto_install:
before_auto_install_commands
dh_auto_install
after_auto_install_commands
See the pybuild manpage for more details (search for BUILD SYSTEM ARGUMENTS)
Each
pybuildcall can be disabled (for given interpreter, version or stage). See thepybuildmanpage for more details (search for--disabledescription).You can pass options in
override_dh_auto_foovia command line options:dh_auto_test -- --system=custom --test-args='{interpreter} setup.py test'or env. variables:
PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS='{interpreter} setup.py test' dh_auto_testYou can export env. variables globally at the beginning of debian/rules
export PYBUILD_TEST_ARGS={dir}/tests/
- via command line, f.e.
override_dh_python3:
dh_python3 --shebang=/usr/bin/python3