unstable as of November 2013) and derivatives, the easiest way to build Python library packages is with the pybuild debhelper build system. There are many ways to build Python libraries for Debian, and each package presents its own corner cases and challenges. The design of this document is to capture best-practices that you can cargo cult into your own packages. The package has some Sphinx-based documentation.įor packages which already support Python 2 and want to add Python 3 support, and/or modernize the packaging as described in this page, it's easiest to do so if your package already uses debhelper (v8 or newer), dh_python2 explicitly, and source format 3.0 (quilt).The package supports at least Python 2.6.For more complex building instructions, you will have to adapt these guidelines. If you can do python setup.py install you'll be fine. Pure-Python or simple extension modules only.
It should have a working setup.py (or for >= Python 3.3 setup.cfg) file and should generally be installable without modification into a virtualenv. A few assumptions about the Python package you are working on are being made: Instead, this page captures in example form, best practices for simple Python libraries that you might find on the Python Package Index. It is not intended to supplant the Debian Python Policy and in fact, if you have not read that document, stop now and go read it. The purpose of this document is to provide a quick style guide for packaging new Python libraries, or adding Python 3 support to existing packages (assuming that upstream supports it too). However, if you are making changes in recommendations, it is requested that you first contact the debian-python mailing list to discuss your changes, unless you're sure they are uncontroversial (e.g. This is a wiki page so of course you are free to edit it.
0 kommentar(er)
