mirror of
https://github.com/python/cpython.git
synced 2025-08-03 16:39:00 +00:00

svn+ssh://pythondev@svn.python.org/python/trunk ................ r67889 | benjamin.peterson | 2008-12-20 19:04:32 -0600 (Sat, 20 Dec 2008) | 1 line sphinx.web is long gone ................ r67890 | benjamin.peterson | 2008-12-20 19:12:26 -0600 (Sat, 20 Dec 2008) | 1 line update readme ................ r67891 | benjamin.peterson | 2008-12-20 19:14:47 -0600 (Sat, 20 Dec 2008) | 1 line there are way too many places which need to have the current version added ................ r67892 | benjamin.peterson | 2008-12-20 19:29:32 -0600 (Sat, 20 Dec 2008) | 9 lines Merged revisions 67809 via svnmerge from svn+ssh://pythondev@svn.python.org/sandbox/trunk/2to3/lib2to3 ........ r67809 | benjamin.peterson | 2008-12-15 21:54:45 -0600 (Mon, 15 Dec 2008) | 1 line fix logic error ........ ................ r67895 | neal.norwitz | 2008-12-21 08:28:32 -0600 (Sun, 21 Dec 2008) | 2 lines Add Tarek for work on distutils. ................ r67898 | benjamin.peterson | 2008-12-21 15:00:53 -0600 (Sun, 21 Dec 2008) | 1 line compute DISTVERSION with patchlevel.py ................ r67904 | benjamin.peterson | 2008-12-22 14:44:58 -0600 (Mon, 22 Dec 2008) | 1 line less attitude ................ r67905 | benjamin.peterson | 2008-12-22 14:51:15 -0600 (Mon, 22 Dec 2008) | 1 line fix #4720: the format to PyArg_ParseTupleAndKeywords can now start with '|' ................ r67906 | benjamin.peterson | 2008-12-22 14:52:53 -0600 (Mon, 22 Dec 2008) | 1 line add NEWS note ................ r67907 | benjamin.peterson | 2008-12-22 16:12:19 -0600 (Mon, 22 Dec 2008) | 1 line silence compiler warning ................ r67912 | georg.brandl | 2008-12-23 06:37:21 -0600 (Tue, 23 Dec 2008) | 2 lines Fix missing "svn" command. ................ r67918 | georg.brandl | 2008-12-23 09:44:25 -0600 (Tue, 23 Dec 2008) | 2 lines Markup fix. ................ r67920 | benjamin.peterson | 2008-12-23 14:09:28 -0600 (Tue, 23 Dec 2008) | 1 line use a global variable, so the compiler doesn't optimize the assignment out ................ r67921 | benjamin.peterson | 2008-12-23 14:12:33 -0600 (Tue, 23 Dec 2008) | 1 line make global static ................ r67923 | benjamin.peterson | 2008-12-24 09:10:27 -0600 (Wed, 24 Dec 2008) | 1 line #4736 BufferRWPair.closed shouldn't try to call another property as a function ................ r67924 | benjamin.peterson | 2008-12-24 10:10:05 -0600 (Wed, 24 Dec 2008) | 1 line pretend exceptions don't exist a while longer ................ r67926 | tarek.ziade | 2008-12-24 13:10:05 -0600 (Wed, 24 Dec 2008) | 1 line fixed #4400 : distutils .pypirc default generated file was broken. ................ r67927 | benjamin.peterson | 2008-12-26 17:26:30 -0600 (Fri, 26 Dec 2008) | 1 line python version is included in file name now ................ r67930 | hirokazu.yamamoto | 2008-12-26 22:19:48 -0600 (Fri, 26 Dec 2008) | 2 lines Issue #4740: Use HIGHEST_PROTOCOL in pickle test. (There is no behavior difference in 2.x because HIGHEST_PROTOCOL == 2) ................ r67943 | alexandre.vassalotti | 2008-12-27 04:02:59 -0600 (Sat, 27 Dec 2008) | 2 lines Fix bogus unicode tests in pickletester. ................
151 lines
5.5 KiB
ReStructuredText
151 lines
5.5 KiB
ReStructuredText
.. highlightlang:: none
|
|
|
|
.. _using-on-unix:
|
|
|
|
********************************
|
|
Using Python on Unix platforms
|
|
********************************
|
|
|
|
.. sectionauthor:: Shriphani Palakodety
|
|
|
|
|
|
Getting and installing the latest version of Python
|
|
===================================================
|
|
|
|
On Linux
|
|
--------
|
|
|
|
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::
|
|
|
|
http://www.linux.com/articles/60383
|
|
for Debian users
|
|
http://linuxmafia.com/pub/linux/suse-linux-internals/chapter35.html
|
|
for OpenSuse users
|
|
http://docs.fedoraproject.org/drafts/rpm-guide-en/ch-creating-rpms.html
|
|
for Fedora users
|
|
http://www.slackbook.org/html/package-management-making-packages.html
|
|
for Slackware users
|
|
|
|
|
|
On FreeBSD and OpenBSD
|
|
----------------------
|
|
|
|
* FreeBSD users, to add the package use::
|
|
|
|
pkg_add -r python
|
|
|
|
* OpenBSD users use::
|
|
|
|
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
|
|
|
|
|
|
On OpenSolaris
|
|
--------------
|
|
|
|
To install the newest Python versions on OpenSolaris, install blastwave
|
|
(http://www.blastwave.org/howto.html) and type "pkg_get -i python" at the
|
|
prompt.
|
|
|
|
|
|
Building Python
|
|
===============
|
|
|
|
If you want to compile CPython yourself, first thing you should do is get the
|
|
`source <http://python.org/download/source/>`_. You can download either the
|
|
latest release's source or just grab a fresh `checkout
|
|
<http://www.python.org/dev/faq/#how-do-i-get-a-checkout-of-the-repository-read-only-and-read-write>`_.
|
|
|
|
The build process consists the usual ::
|
|
|
|
./configure
|
|
make
|
|
make install
|
|
|
|
invocations. Configuration options and caveats for specific Unix platforms are
|
|
extensively documented in the :file:`README` file in the root of the Python
|
|
source tree.
|
|
|
|
.. warning::
|
|
|
|
``make install`` can overwrite or masquerade the :file:`python` binary.
|
|
``make altinstall`` is therefore recommended instead of ``make install``
|
|
since it only installs :file:`{exec_prefix}/bin/python{version}`.
|
|
|
|
|
|
Python-related paths and files
|
|
==============================
|
|
|
|
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/python` | Recommended location of the interpreter. |
|
|
+-----------------------------------------------+------------------------------------------+
|
|
| :file:`{prefix}/lib/python{version}`, | Recommended locations of the directories |
|
|
| :file:`{exec_prefix}/lib/python{version}` | containing the standard modules. |
|
|
+-----------------------------------------------+------------------------------------------+
|
|
| :file:`{prefix}/include/python{version}`, | Recommended locations of the directories |
|
|
| :file:`{exec_prefix}/include/python{version}` | containing the include files needed for |
|
|
| | developing Python extensions and |
|
|
| | embedding the interpreter. |
|
|
+-----------------------------------------------+------------------------------------------+
|
|
| :file:`~/.pythonrc.py` | User-specific initialization file loaded |
|
|
| | by the user module; not used by default |
|
|
| | or by most applications. |
|
|
+-----------------------------------------------+------------------------------------------+
|
|
|
|
|
|
Miscellaneous
|
|
=============
|
|
|
|
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 python
|
|
|
|
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/python`` as the interpreter path.
|
|
|
|
To use shell commands in your python scripts, look at the :mod:`subprocess` module.
|
|
|
|
|
|
Editors
|
|
=======
|
|
|
|
Vim and Emacs are excellent editors which support Python very well. For more
|
|
information on how to code in python in these editors, look at:
|
|
|
|
* http://www.vim.org/scripts/script.php?script_id=790
|
|
* http://sourceforge.net/projects/python-mode
|
|
|
|
Geany is an excellent IDE with support for a lot of languages. For more
|
|
information, read: http://geany.uvena.de/
|
|
|
|
Komodo edit is another extremely good IDE. It also has support for a lot of
|
|
languages. For more information, read:
|
|
http://www.activestate.com/store/productdetail.aspx?prdGuid=20f4ed15-6684-4118-a78b-d37ff4058c5f
|