Difference between revisions of "Python package guidelines"
(minor formatting changes) |
m (→Notes) |
||
| Line 14: | Line 14: | ||
== Notes == | == Notes == | ||
| − | The {{Ic|--optimize}} parameter compiles {{Ic|.pyo}} files so they can be tracked by [[pacman]]. | + | The {{Ic|--optimize=1}} parameter compiles {{Ic|.pyo}} files so they can be tracked by [[pacman]]. |
In most cases, you should put {{Ic|any}} in the {{Ic|arch}} array since most Python packages are architecture independent. | In most cases, you should put {{Ic|any}} in the {{Ic|arch}} array since most Python packages are architecture independent. | ||
Revision as of 18:40, 28 August 2012
Writing PKGBUILDs for software written in Python.
Contents
Package Naming
For libraries, use python-modulename. For applications, use the program name. In either case, the package name should be entirely lowercase.
Python 2 libraries should instead be named python2-modulename.
File Placement
Most Python packages are installed with the distutils system using setup.py, which installs files under /usr/lib/python<python version>/site-packages/pkgname directory.
Notes
The.pyo files so they can be tracked by pacman.
In most cases, you should put any in the arch array since most Python packages are architecture independent.
Please do not install a directory named just tests, as it easily conflicts with other Python packages (for example, /usr/lib/python2.7/site-packages/tests/).
Example
An example PKGBUILD can be found at /usr/share/pacman/PKGBUILD-python.proto, which is in the abs package.