.. sectionauthor:: Shriphani Palakodety
Python comes preinstalled on most Linux distributions, and is available as a package on all others. However there are certain features you might want to use that are not available on your distro's package. You can easily compile the latest version of Python from source.
In the event that Python doesn't come preinstalled and isn't in the repositories as well, you can easily make packages for your own distro. Have a look at the following links:
.. seealso::
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
FreeBSD users, to add the package use:
pkg install python3
OpenBSD users, to add the package use:
pkg_add -r python
pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/<insert your architecture here>/python-<version>.tgz
For example i386 users get the 2.5.1 version of Python using:
pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/i386/python-2.5.1p2.tgz
You can get Python from Building Python
If you want to compile CPython yourself, first thing you should do is get the clone. (If you want to contribute patches, you will need a clone.)
The build process consists of the usual commands:
./configure
make
make install
Configuration options and caveats for specific Unix platforms are extensively documented in the :source:`README.rst` file in the root of the Python source tree.
Warning
make install can overwrite or masquerade the :file:`python3` binary.
make altinstall is therefore recommended instead of make install
since it only installs :file:`{exec_prefix}/bin/python{version}`.
These are subject to difference depending on local installation conventions;
:envvar:`prefix` (${prefix}) and :envvar:`exec_prefix` (${exec_prefix})
are installation-dependent and should be interpreted as for GNU software; they
may be the same.
For example, on most Linux systems, the default for both is :file:`/usr`.
| File/directory | Meaning |
|---|---|
| :file:`{exec_prefix}/bin/python3` | Recommended location of the interpreter. |
| :file:`{prefix}/lib/python{version}`, :file:`{exec_prefix}/lib/python{version}` | Recommended locations of the directories containing the standard modules. |
| :file:`{prefix}/include/python{version}`, :file:`{exec_prefix}/include/python{version}` | Recommended locations of the directories containing the include files needed for developing Python extensions and embedding the interpreter. |
To easily use Python scripts on Unix, you need to make them executable, e.g. with
$ chmod +x script
and put an appropriate Shebang line at the top of the script. A good choice is usually
#!/usr/bin/env python3
which searches for the Python interpreter in the whole :envvar:`PATH`. However,
some Unices may not have the :program:`env` command, so you may need to hardcode
/usr/bin/python3 as the interpreter path.
To use shell commands in your Python scripts, look at the :mod:`subprocess` module.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。