You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

148 lines
5.2 KiB

Merged revisions 61038,61042-61045,61047,61050,61053,61055-61056,61061-61062,61066,61068,61070,61081-61095 via svnmerge from svn+ssh://pythondev@svn.python.org/python/trunk ........ r61081 | neal.norwitz | 2008-02-26 09:04:59 +0100 (Tue, 26 Feb 2008) | 7 lines Speed up this test by about 99%. Remove sleeps and replace with events. (This may fail on some slow platforms, but we can fix those cases which should be relatively isolated and easier to find now.) Move two test cases that didn't require a server to be started to a separate TestCase. These tests were taking 3 seconds which is what the timeout was set to. ........ r61082 | christian.heimes | 2008-02-26 09:18:11 +0100 (Tue, 26 Feb 2008) | 1 line The contains function raised a gcc warning. The new code is copied straight from py3k. ........ r61084 | neal.norwitz | 2008-02-26 09:21:28 +0100 (Tue, 26 Feb 2008) | 3 lines Add a timing flag to Trace so you can see where slowness occurs like waiting for socket timeouts in test_smtplib :-). ........ r61086 | christian.heimes | 2008-02-26 18:23:51 +0100 (Tue, 26 Feb 2008) | 3 lines Patch #1691070 from Roger Upole: Speed up PyArg_ParseTupleAndKeywords() and improve error msg My tests don't show the promised speed up of 10%. The code is as fast as the old code for simple cases and slightly faster for complex cases with several of args and kwargs. But the patch simplifies the code, too. ........ r61087 | georg.brandl | 2008-02-26 20:13:45 +0100 (Tue, 26 Feb 2008) | 2 lines #2194: fix some typos. ........ r61088 | raymond.hettinger | 2008-02-27 00:40:50 +0100 (Wed, 27 Feb 2008) | 1 line Add itertools.combinations(). ........ r61089 | raymond.hettinger | 2008-02-27 02:08:04 +0100 (Wed, 27 Feb 2008) | 1 line One too many decrefs. ........ r61090 | raymond.hettinger | 2008-02-27 02:08:30 +0100 (Wed, 27 Feb 2008) | 1 line Larger test range ........ r61091 | raymond.hettinger | 2008-02-27 02:44:34 +0100 (Wed, 27 Feb 2008) | 1 line Simply the sample code for combinations(). ........
19 years ago
Merged revisions 67889-67892,67895,67898,67904-67907,67912,67918,67920-67921,67923-67924,67926-67927,67930,67943 via svnmerge from 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. ................
18 years ago
  1. .. highlightlang:: sh
  2. .. _using-on-unix:
  3. ********************************
  4. Using Python on Unix platforms
  5. ********************************
  6. .. sectionauthor:: Shriphani Palakodety
  7. Getting and installing the latest version of Python
  8. ===================================================
  9. On Linux
  10. --------
  11. Python comes preinstalled on most Linux distributions, and is available as a
  12. package on all others. However there are certain features you might want to use
  13. that are not available on your distro's package. You can easily compile the
  14. latest version of Python from source.
  15. In the event that Python doesn't come preinstalled and isn't in the repositories as
  16. well, you can easily make packages for your own distro. Have a look at the
  17. following links:
  18. .. seealso::
  19. http://www.debian.org/doc/manuals/maint-guide/first.en.html
  20. for Debian users
  21. http://en.opensuse.org/Portal:Packaging
  22. for OpenSuse users
  23. http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-creating-rpms.html
  24. for Fedora users
  25. http://www.slackbook.org/html/package-management-making-packages.html
  26. for Slackware users
  27. On FreeBSD and OpenBSD
  28. ----------------------
  29. * FreeBSD users, to add the package use::
  30. pkg_add -r python
  31. * OpenBSD users use::
  32. pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/<insert your architecture here>/python-<version>.tgz
  33. For example i386 users get the 2.5.1 version of Python using::
  34. pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/i386/python-2.5.1p2.tgz
  35. On OpenSolaris
  36. --------------
  37. To install the newest Python versions on OpenSolaris, install `blastwave
  38. <http://www.blastwave.org/howto.html>`_ and type ``pkg_get -i python`` at the
  39. prompt.
  40. Building Python
  41. ===============
  42. If you want to compile CPython yourself, first thing you should do is get the
  43. `source <http://python.org/download/source/>`_. You can download either the
  44. latest release's source or just grab a fresh `clone
  45. <http://docs.python.org/devguide/setup#getting-the-source-code>`_. (If you want
  46. to contribute patches, you will need a clone.)
  47. The build process consists in the usual ::
  48. ./configure
  49. make
  50. make install
  51. invocations. Configuration options and caveats for specific Unix platforms are
  52. extensively documented in the :source:`README` file in the root of the Python
  53. source tree.
  54. .. warning::
  55. ``make install`` can overwrite or masquerade the :file:`python3` binary.
  56. ``make altinstall`` is therefore recommended instead of ``make install``
  57. since it only installs :file:`{exec_prefix}/bin/python{version}`.
  58. Python-related paths and files
  59. ==============================
  60. These are subject to difference depending on local installation conventions;
  61. :envvar:`prefix` (``${prefix}``) and :envvar:`exec_prefix` (``${exec_prefix}``)
  62. are installation-dependent and should be interpreted as for GNU software; they
  63. may be the same.
  64. For example, on most Linux systems, the default for both is :file:`/usr`.
  65. +-----------------------------------------------+------------------------------------------+
  66. | File/directory | Meaning |
  67. +===============================================+==========================================+
  68. | :file:`{exec_prefix}/bin/python3` | Recommended location of the interpreter. |
  69. +-----------------------------------------------+------------------------------------------+
  70. | :file:`{prefix}/lib/python{version}`, | Recommended locations of the directories |
  71. | :file:`{exec_prefix}/lib/python{version}` | containing the standard modules. |
  72. +-----------------------------------------------+------------------------------------------+
  73. | :file:`{prefix}/include/python{version}`, | Recommended locations of the directories |
  74. | :file:`{exec_prefix}/include/python{version}` | containing the include files needed for |
  75. | | developing Python extensions and |
  76. | | embedding the interpreter. |
  77. +-----------------------------------------------+------------------------------------------+
  78. Miscellaneous
  79. =============
  80. To easily use Python scripts on Unix, you need to make them executable,
  81. e.g. with ::
  82. $ chmod +x script
  83. and put an appropriate Shebang line at the top of the script. A good choice is
  84. usually ::
  85. #!/usr/bin/env python3
  86. which searches for the Python interpreter in the whole :envvar:`PATH`. However,
  87. some Unices may not have the :program:`env` command, so you may need to hardcode
  88. ``/usr/bin/python3`` as the interpreter path.
  89. To use shell commands in your Python scripts, look at the :mod:`subprocess` module.
  90. Editors
  91. =======
  92. Vim and Emacs are excellent editors which support Python very well. For more
  93. information on how to code in Python in these editors, look at:
  94. * http://www.vim.org/scripts/script.php?script_id=790
  95. * http://sourceforge.net/projects/python-mode
  96. Geany is an excellent IDE with support for a lot of languages. For more
  97. information, read: http://www.geany.org/
  98. Komodo edit is another extremely good IDE. It also has support for a lot of
  99. languages. For more information, read:
  100. http://www.activestate.com/store/productdetail.aspx?prdGuid=20f4ed15-6684-4118-a78b-d37ff4058c5f