2.Using Python on Unix platforms¶
2.1.Getting and installing the latest version of Python¶
2.1.1.On Linux¶
Python comes preinstalled on most Linux distributions, and is available as apackage on all others. However there are certain features you might want to usethat are not available on your distro’s package. You can easily compile thelatest version of Python from source.
In the event that Python doesn’t come preinstalled and isn’t in the repositories aswell, you can easily make packages for your own distro. Have a look at thefollowing links:
See also
- https://www.debian.org/doc/manuals/maint-guide/first.en.html
for Debian users
- https://en.opensuse.org/Portal:Packaging
for OpenSuse users
- https://docs-old.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-creating-rpms.html
for Fedora users
- http://www.slackbook.org/html/package-management-making-packages.html
for Slackware users
2.1.2.On FreeBSD and OpenBSD¶
FreeBSD users, to add the package use:
pkginstallpython3
OpenBSD users, to add the package use:
pkg_add-rpythonpkg_addftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/<insertyourarchitecturehere>/python-<version>.tgz
For example i386 users get the 2.5.1 version of Python using:
pkg_addftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/i386/python-2.5.1p2.tgz
2.1.3.On OpenSolaris¶
You can get Python fromOpenCSW. Various versionsof Python are available and can be installed with e.g.pkgutil-ipython27.
2.2.Building Python¶
If you want to compile CPython yourself, first thing you should do is get thesource. You can download either thelatest release’s source or just grab a freshclone. (If you wantto contribute patches, you will need a clone.)
The build process consists of the usual commands:
./configuremakemakeinstall
Configuration options and caveats for specific Unix platforms are extensivelydocumented in theREADME.rst file in the root of the Python sourcetree.
Warning
makeinstall can overwrite or masquerade thepython3 binary.makealtinstall is therefore recommended instead ofmakeinstallsince it only installsexec_prefix/bin/pythonversion.
2.3.Python-related paths and files¶
These are subject to difference depending on local installation conventions;prefix (${prefix}) andexec_prefix (${exec_prefix})are installation-dependent and should be interpreted as for GNU software; theymay be the same.
For example, on most Linux systems, the default for both is/usr.
File/directory | Meaning |
|---|---|
| Recommended location of the interpreter. |
| Recommended locations of the directoriescontaining the standard modules. |
| Recommended locations of the directoriescontaining the include files needed fordeveloping Python extensions andembedding the interpreter. |
2.4.Miscellaneous¶
To easily use Python scripts on Unix, you need to make them executable,e.g. with
$chmod+xscriptand put an appropriate Shebang line at the top of the script. A good choice isusually
#!/usr/bin/env python3which searches for the Python interpreter in the wholePATH. However,some Unices may not have theenv command, so you may need to hardcode/usr/bin/python3 as the interpreter path.
To use shell commands in your Python scripts, look at thesubprocess module.