Difference between revisions of "Python package guidelines"

From ArchWiki
Jump to: navigation, search
m (whitespace)
(complete sentence article summary)
Line 2: Line 2:
 
[[it:Python Package Guidelines]]
 
[[it:Python Package Guidelines]]
 
{{Package Guidelines}}
 
{{Package Guidelines}}
Writing [[PKGBUILD]]s for software written in [[Python]].
+
This document covers standards and guidelines on writing [[PKGBUILD]]s for [[Python]] software.
  
 
== Package naming ==
 
== Package naming ==

Revision as of 01:21, 11 August 2014

Template:Package Guidelines This document covers standards and guidelines on writing PKGBUILDs for Python software.

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 --optimize=1 parameter compiles .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 here or at /usr/share/pacman/PKGBUILD-python.proto, which is in the abs package.