mirror of https://github.com/python/cpython
65580e875f
................ r76001 | antoine.pitrou | 2009-11-01 00:19:52 +0100 (So, 01 Nov 2009) | 3 lines Use richer assertions in test_mailbox (for better failure messages). ................ r76003 | antoine.pitrou | 2009-11-01 01:30:13 +0100 (So, 01 Nov 2009) | 6 lines Hopefully fix the buildbot problems on test_mailbox, by computing the maildir toc cache refresh date before actually refreshing the cache. (see #6896) ................ r76007 | antoine.pitrou | 2009-11-01 12:58:22 +0100 (So, 01 Nov 2009) | 3 lines Buffered I/O: optimize lock taking in the common non-contended case. ................ r76016 | gregory.p.smith | 2009-11-01 19:33:55 +0100 (So, 01 Nov 2009) | 2 lines news entry for r76000 ................ r76025 | raymond.hettinger | 2009-11-01 21:45:16 +0100 (So, 01 Nov 2009) | 1 line Fix exception handling in itertools.izip_longest(). ................ r76028 | gregory.p.smith | 2009-11-01 22:02:52 +0100 (So, 01 Nov 2009) | 2 lines issue1115: convert some AC_TRY_RUNs into AC_TRY_COMPILEs. ................ r76029 | gregory.p.smith | 2009-11-01 22:03:38 +0100 (So, 01 Nov 2009) | 2 lines configure generated from r76028 ................ r76034 | antoine.pitrou | 2009-11-01 22:29:33 +0100 (So, 01 Nov 2009) | 3 lines This should finally fix #6896. Let's watch the buildbots. ................ r76047 | antoine.pitrou | 2009-11-02 00:54:20 +0100 (Mo, 02 Nov 2009) | 3 lines Fix and improve some assertions in test_site ................ r76051 | gregory.p.smith | 2009-11-02 02:38:35 +0100 (Mo, 02 Nov 2009) | 2 lines build using r76050 ................ r76052 | gregory.p.smith | 2009-11-02 03:02:38 +0100 (Mo, 02 Nov 2009) | 5 lines see issue1006238, this merges in the following patch to ease cross compiling the printf %zd check. http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-lang/python/files/python-2.5-cross-printf.patch?rev=1.1&view=markup ................ r76053 | gregory.p.smith | 2009-11-02 03:03:16 +0100 (Mo, 02 Nov 2009) | 2 lines regenerated from r76052 ................ r76054 | antoine.pitrou | 2009-11-02 12:34:27 +0100 (Mo, 02 Nov 2009) | 3 lines Since r76034 was successful, add a NEWS entry for it. ................ r76057 | benjamin.peterson | 2009-11-02 16:06:45 +0100 (Mo, 02 Nov 2009) | 1 line prevent a rather unlikely segfault ................ r76058 | benjamin.peterson | 2009-11-02 17:14:19 +0100 (Mo, 02 Nov 2009) | 1 line grant list.index() a more informative error message #7252 ................ r76062 | benjamin.peterson | 2009-11-02 19:12:12 +0100 (Mo, 02 Nov 2009) | 70 lines Merged revisions 74359,75081,75088,75213,75278,75303,75427-75428,75734-75736,75865,76059-76061 via svnmerge from svn+ssh://pythondev@svn.python.org/sandbox/trunk/2to3/lib2to3 ........ r74359 | benjamin.peterson | 2009-08-12 17:23:13 -0500 (Wed, 12 Aug 2009) | 1 line don't pass the deprecated print_function option ........ r75081 | benjamin.peterson | 2009-09-26 22:02:57 -0500 (Sat, 26 Sep 2009) | 1 line let 2to3 work with extended iterable unpacking ........ r75088 | benjamin.peterson | 2009-09-27 11:25:21 -0500 (Sun, 27 Sep 2009) | 1 line look on the type only for __call__ ........ r75213 | benjamin.peterson | 2009-10-03 10:09:46 -0500 (Sat, 03 Oct 2009) | 5 lines revert 75212; it's not correct People can use isinstance(x, collections.Callable) if they expect objects with __call__ in their instance dictionaries. ........ r75278 | benjamin.peterson | 2009-10-07 16:25:56 -0500 (Wed, 07 Oct 2009) | 4 lines fix whitespace problems with fix_idioms #3563 Patch by Joe Amenta. ........ r75303 | benjamin.peterson | 2009-10-09 16:59:11 -0500 (Fri, 09 Oct 2009) | 1 line port latin-1 and utf-8 cookie improvements ........ r75427 | benjamin.peterson | 2009-10-14 20:35:57 -0500 (Wed, 14 Oct 2009) | 1 line force floor division ........ r75428 | benjamin.peterson | 2009-10-14 20:39:21 -0500 (Wed, 14 Oct 2009) | 1 line silence -3 warnings about __hash__ ........ r75734 | benjamin.peterson | 2009-10-26 16:25:53 -0500 (Mon, 26 Oct 2009) | 2 lines warn on map(None, ...) with more than 2 arguments #7203 ........ r75735 | benjamin.peterson | 2009-10-26 16:28:25 -0500 (Mon, 26 Oct 2009) | 1 line remove unused result ........ r75736 | benjamin.peterson | 2009-10-26 16:29:02 -0500 (Mon, 26 Oct 2009) | 1 line using get() here is a bit pointless ........ r75865 | benjamin.peterson | 2009-10-27 15:49:00 -0500 (Tue, 27 Oct 2009) | 1 line explain reason for warning ........ r76059 | benjamin.peterson | 2009-11-02 11:43:47 -0600 (Mon, 02 Nov 2009) | 1 line tuples are no longer used for children ........ r76060 | benjamin.peterson | 2009-11-02 11:55:40 -0600 (Mon, 02 Nov 2009) | 1 line revert r76059; apparently some fixers rely on Leaf no () for children ........ r76061 | benjamin.peterson | 2009-11-02 12:06:17 -0600 (Mon, 02 Nov 2009) | 1 line make fix_tuple_params keep the tree valid #7253 ........ ................ r76064 | benjamin.peterson | 2009-11-02 19:16:36 +0100 (Mo, 02 Nov 2009) | 1 line add space ................ r76066 | benjamin.peterson | 2009-11-02 19:22:53 +0100 (Mo, 02 Nov 2009) | 9 lines Merged revisions 76065 via svnmerge from svn+ssh://pythondev@svn.python.org/sandbox/trunk/2to3/lib2to3 ........ r76065 | benjamin.peterson | 2009-11-02 12:21:25 -0600 (Mon, 02 Nov 2009) | 1 line don't print stuff in tests ........ ................ r76067 | benjamin.peterson | 2009-11-02 19:24:57 +0100 (Mo, 02 Nov 2009) | 1 line enable test_parser in lib2to3 ................ r76108 | antoine.pitrou | 2009-11-04 20:25:14 +0100 (Mi, 04 Nov 2009) | 6 lines Issue #7211: Allow 64-bit values for the `ident` and `data` fields of kevent objects on 64-bit systems. Patch by Michael Broghton. I will revert this checkin if it causes problems on our BSD buildbots. ................ r76126 | benjamin.peterson | 2009-11-05 22:29:56 +0100 (Do, 05 Nov 2009) | 9 lines Merged revisions 76125 via svnmerge from svn+ssh://pythondev@svn.python.org/sandbox/trunk/2to3/lib2to3 ........ r76125 | benjamin.peterson | 2009-11-05 15:26:55 -0600 (Thu, 05 Nov 2009) | 1 line handle newline issues better for comparing files ........ ................ r76129 | benjamin.peterson | 2009-11-06 00:20:06 +0100 (Fr, 06 Nov 2009) | 13 lines Merged revisions 76127-76128 via svnmerge from svn+ssh://pythondev@svn.python.org/sandbox/trunk/2to3/lib2to3 ........ r76127 | benjamin.peterson | 2009-11-05 17:04:58 -0600 (Thu, 05 Nov 2009) | 1 line set svn:eol-style ........ r76128 | benjamin.peterson | 2009-11-05 17:07:46 -0600 (Thu, 05 Nov 2009) | 1 line skip this test on windows to avoid newline horrors ........ ................ r76132 | benjamin.peterson | 2009-11-06 00:54:42 +0100 (Fr, 06 Nov 2009) | 9 lines Merged revisions 76131 via svnmerge from svn+ssh://pythondev@svn.python.org/sandbox/trunk/2to3/lib2to3 ........ r76131 | benjamin.peterson | 2009-11-05 17:53:21 -0600 (Thu, 05 Nov 2009) | 1 line import sys ........ ................ r76139 | benjamin.peterson | 2009-11-07 02:04:38 +0100 (Sa, 07 Nov 2009) | 1 line spelling ................ r76140 | nick.coghlan | 2009-11-07 09:13:55 +0100 (Sa, 07 Nov 2009) | 1 line Add test for runpy.run_module package execution and use something other than logging as the example of a non-executable package ................ r76141 | nick.coghlan | 2009-11-07 09:15:01 +0100 (Sa, 07 Nov 2009) | 1 line Some minor cleanups to private runpy code and docstrings ................ r76154 | brett.cannon | 2009-11-08 22:35:28 +0100 (So, 08 Nov 2009) | 4 lines Properly detect whether a C file is using tabs or spaces for Vim. Closes issue #5611. Thanks Kirk McDonald and Johannes Hoff. ................ r76162 | benjamin.peterson | 2009-11-09 05:10:53 +0100 (Mo, 09 Nov 2009) | 1 line discuss how to use -p ................ r76176 | mark.dickinson | 2009-11-09 18:03:34 +0100 (Mo, 09 Nov 2009) | 7 lines Issue #7251: Break out round tests for large values into a separate test function, and skip that test on Linux/alpha systems with a broken system round function. This should turn the Debian/alpha buildbot green. ................ r76194 | raymond.hettinger | 2009-11-10 20:35:55 +0100 (Di, 10 Nov 2009) | 3 lines Show example of how to make a sorted dictionary ................ r76196 | antoine.pitrou | 2009-11-10 21:49:30 +0100 (Di, 10 Nov 2009) | 8 lines Issue #7197: Allow unittest.TextTestRunner objects to be pickled and unpickled. This fixes crashes under Windows when trying to run test_multiprocessing in verbose mode. Additionally, Test_TextTestRunner hadn't been enabled in test_unittest. ................ r76199 | antoine.pitrou | 2009-11-10 22:39:25 +0100 (Di, 10 Nov 2009) | 3 lines Backport micro-fix from the py3k svnmerge ................ r76230 | benjamin.peterson | 2009-11-13 00:39:44 +0100 (Fr, 13 Nov 2009) | 2 lines fix several compile() issues by translating newlines in the tokenizer ................ r76231 | benjamin.peterson | 2009-11-13 00:42:23 +0100 (Fr, 13 Nov 2009) | 1 line this main is much more useful ................ r76243 | benjamin.peterson | 2009-11-13 23:17:17 +0100 (Fr, 13 Nov 2009) | 1 line never mind about eval mode in this case ................ r76249 | benjamin.peterson | 2009-11-13 23:56:00 +0100 (Fr, 13 Nov 2009) | 1 line revert r76243; I was right, actually :) ................ r76260 | r.david.murray | 2009-11-14 16:18:22 +0100 (Sa, 14 Nov 2009) | 5 lines Issue #7312 (new feature): Add a -F flag to run the selected tests in a loop until a test fails. Can be combined with -j. Patch by Antoine Pitrou. ................ r76286 | nick.coghlan | 2009-11-15 08:30:34 +0100 (So, 15 Nov 2009) | 1 line Issue #6816: expose the zipfile and directory execution mechanism to Python code via the runpy module. Also consolidated some script execution functionality in the test harness into a helper module and removed some implementation details from the runpy module documentation. ................ r76300 | mark.dickinson | 2009-11-15 14:12:43 +0100 (So, 15 Nov 2009) | 3 lines Issue #5792: Extend short float repr support to x86 platforms using suncc or icc. Many thanks Stefan Krah for help and OpenSolaris testing. ................ r76306 | antoine.pitrou | 2009-11-15 15:10:48 +0100 (So, 15 Nov 2009) | 4 lines Issue #4969: The mimetypes module now reads the MIME database from the registry under Windows. Patch by Gabriel Genellina. ................ r76308 | mark.dickinson | 2009-11-15 17:18:58 +0100 (So, 15 Nov 2009) | 3 lines Issue #7228: Add '%lld' and '%llu' support to PyFormat_FromString, PyFormat_FromStringV and PyErr_Format. ................ r76309 | antoine.pitrou | 2009-11-15 18:22:09 +0100 (So, 15 Nov 2009) | 4 lines Issue #2054: ftplib now provides an FTP_TLS class to do secure FTP using TLS or SSL. Patch by Giampaolo Rodola'. ................ r76321 | nick.coghlan | 2009-11-16 04:55:51 +0100 (Mo, 16 Nov 2009) | 1 line Account for another cache when hunting ref leaks ................ r76322 | nick.coghlan | 2009-11-16 04:57:32 +0100 (Mo, 16 Nov 2009) | 1 line Allow for backslashes in file paths passed to the regex engine ................ r76333 | mark.dickinson | 2009-11-16 20:17:16 +0100 (Mo, 16 Nov 2009) | 1 line Silence another MSVC warning about unary minus. ................ r76337 | philip.jenvey | 2009-11-17 03:42:26 +0100 (Di, 17 Nov 2009) | 2 lines #1757126: fix typo with the cyrillic_asian alias ................ r76358 | tarek.ziade | 2009-11-18 09:46:56 +0100 (Mi, 18 Nov 2009) | 1 line #7293: distutils.test_msvc9compiler now uses a key that exists on any fresh windows install ................ r76362 | nick.coghlan | 2009-11-18 12:27:53 +0100 (Mi, 18 Nov 2009) | 1 line Correctly escape arbitrary error message text in the runpy unit tests ................ r76367 | georg.brandl | 2009-11-18 19:52:35 +0100 (Mi, 18 Nov 2009) | 1 line Make separate section for deprecations in 2.7 whatsnew. ................ r76373 | mark.dickinson | 2009-11-18 20:33:35 +0100 (Mi, 18 Nov 2009) | 5 lines Issue #7117, continued: Change round implementation to use the correctly-rounded string <-> float conversions; this makes sure that the result of the round operation is correctly rounded, and hence displays nicely using the new float repr. ................ r76379 | mark.dickinson | 2009-11-18 21:14:57 +0100 (Mi, 18 Nov 2009) | 1 line Enable short float repr! ................ r76380 | antoine.pitrou | 2009-11-18 21:20:46 +0100 (Mi, 18 Nov 2009) | 3 lines Mention Giampolo R's new FTP TLS support in the what's new file ................ r76382 | raymond.hettinger | 2009-11-18 21:28:22 +0100 (Mi, 18 Nov 2009) | 1 line Issue 7263: Fix set.intersection() docstring. ................ r76392 | raymond.hettinger | 2009-11-19 02:22:04 +0100 (Do, 19 Nov 2009) | 1 line Fix docstrings for itertools combinatoric functions. ................ r76399 | tarek.ziade | 2009-11-19 06:33:16 +0100 (Do, 19 Nov 2009) | 1 line dragfullwindows can have value 2 ................ r76411 | mark.dickinson | 2009-11-19 19:41:49 +0100 (Do, 19 Nov 2009) | 1 line Misc/NEWS entries for issue 7117. ................ r76428 | benjamin.peterson | 2009-11-20 03:15:50 +0100 (Fr, 20 Nov 2009) | 1 line turn goto into do while loop ................ r76429 | benjamin.peterson | 2009-11-20 03:56:43 +0100 (Fr, 20 Nov 2009) | 2 lines avoid doing an uneeded import in a function ................ r76431 | mark.dickinson | 2009-11-20 20:27:43 +0100 (Fr, 20 Nov 2009) | 1 line Regenerate configure with GNU autoconf 2.61. ................ r76432 | mark.dickinson | 2009-11-20 20:30:22 +0100 (Fr, 20 Nov 2009) | 5 lines Issue #7272: Add configure test to detect whether sem_open works properly, and use this to skip test_multiprocessing on platforms where sem_open raises a signal. This should fix some FreeBSD buildbot failures for test_multiprocessing. ................ r76434 | jesse.noller | 2009-11-21 15:06:24 +0100 (Sa, 21 Nov 2009) | 1 line revert unintended change to multiprocessing/queues.py ................ r76438 | jesse.noller | 2009-11-21 15:38:23 +0100 (Sa, 21 Nov 2009) | 1 line issue6615: Additional test for logging support in multiprocessing ................ r76443 | lars.gustaebel | 2009-11-22 19:30:53 +0100 (So, 22 Nov 2009) | 24 lines Issue #6123: Fix opening empty archives and files. (Note that an empty archive is not the same as an empty file. An empty archive contains no members and is correctly terminated with an EOF block full of zeros. An empty file contains no data at all.) The problem was that although tarfile was able to create empty archives, it failed to open them raising a ReadError. On the other hand, tarfile opened empty files without error in most read modes and presented them as empty archives. (However, some modes still raised errors: "r|gz" raised ReadError, but "r:gz" worked, "r:bz2" even raised EOFError.) In order to get a more fine-grained control over the various internal error conditions I now split up the HeaderError exception into a number of meaningful sub-exceptions. This makes it easier in the TarFile.next() method to react to the different conditions in the correct way. The visible change in its behaviour now is that tarfile will open empty archives correctly and raise ReadError consistently for empty files. ................ r76465 | mark.dickinson | 2009-11-23 19:46:41 +0100 (Mo, 23 Nov 2009) | 4 lines Remove restriction on precision when formatting floats. This is the first step towards removing the %f -> %g switch (see issues 7117, 5859). ................ r76472 | mark.dickinson | 2009-11-23 21:54:09 +0100 (Mo, 23 Nov 2009) | 4 lines Issue #7117, continued: Remove substitution of %g-style formatting for %f-style formatting, which used to occur at high precision. Float formatting should now be consistent between 2.7 and 3.1. ................ r76483 | mark.dickinson | 2009-11-24 11:54:58 +0100 (Di, 24 Nov 2009) | 2 lines round(0, "ermintrude") succeeded instead of producing a TypeError. Fix this. ................ r76487 | jesse.noller | 2009-11-24 15:17:29 +0100 (Di, 24 Nov 2009) | 1 line comment out test added in r76438, which caused refleaks ................ r76489 | mark.dickinson | 2009-11-24 15:27:02 +0100 (Di, 24 Nov 2009) | 1 line Fix some documentation examples involving the repr of a float. ................ r76495 | mark.dickinson | 2009-11-24 16:12:20 +0100 (Di, 24 Nov 2009) | 2 lines Issue #7117: Update float formatting testcases to match those in py3k. ................ r76498 | vinay.sajip | 2009-11-24 16:53:25 +0100 (Di, 24 Nov 2009) | 1 line Made logging classes new-style and added name property to handlers. ................ r76502 | mark.dickinson | 2009-11-24 21:51:48 +0100 (Di, 24 Nov 2009) | 3 lines Issue #7228: Fix format mismatch when printing something of type off_t. (Should silence some compiler warnings.) ................ r76507 | vinay.sajip | 2009-11-25 10:03:30 +0100 (Mi, 25 Nov 2009) | 1 line Issue #6615: logging: Used weak references in internal handler list. Thanks to flox (Florent Xicluna) for the patch. ................ r76508 | vinay.sajip | 2009-11-25 10:22:47 +0100 (Mi, 25 Nov 2009) | 1 line logging: made _handlers a WeakValueDictionary. ................ r76509 | vinay.sajip | 2009-11-25 15:12:03 +0100 (Mi, 25 Nov 2009) | 1 line logging: Issue 6615: Changed handler prepend to append. ................ r76517 | benjamin.peterson | 2009-11-25 19:16:46 +0100 (Mi, 25 Nov 2009) | 29 lines Merged revisions 76160-76161,76250,76252,76447,76506 via svnmerge from svn+ssh://pythondev@svn.python.org/sandbox/trunk/2to3/lib2to3 ........ r76160 | benjamin.peterson | 2009-11-08 18:53:48 -0600 (Sun, 08 Nov 2009) | 1 line undeprecate the -p option; it's useful for converting python3 sources ........ r76161 | benjamin.peterson | 2009-11-08 19:05:37 -0600 (Sun, 08 Nov 2009) | 1 line simplify condition ........ r76250 | benjamin.peterson | 2009-11-13 16:56:48 -0600 (Fri, 13 Nov 2009) | 1 line fix handling of a utf-8 bom #7313 ........ r76252 | benjamin.peterson | 2009-11-13 16:58:36 -0600 (Fri, 13 Nov 2009) | 1 line remove pdb turd ........ r76447 | benjamin.peterson | 2009-11-22 18:17:40 -0600 (Sun, 22 Nov 2009) | 1 line #7375 fix nested transformations in fix_urllib ........ r76506 | benjamin.peterson | 2009-11-24 18:34:31 -0600 (Tue, 24 Nov 2009) | 1 line use generator expressions in any() ........ ................ r76522 | barry.warsaw | 2009-11-25 19:38:32 +0100 (Mi, 25 Nov 2009) | 2 lines Add mktime_tz to __all__. It's documented as being available in email.utils. ................ r76529 | antoine.pitrou | 2009-11-25 23:59:36 +0100 (Mi, 25 Nov 2009) | 4 lines Issue #5788: `datetime.timedelta` objects get a new `total_seconds()` method returning the total number of seconds in the duration. Patch by Brian Quinlan. ................ r76531 | antoine.pitrou | 2009-11-26 00:03:22 +0100 (Do, 26 Nov 2009) | 3 lines Forgot to add a `versionadded` tag ................ r76534 | martin.v.loewis | 2009-11-26 09:42:05 +0100 (Do, 26 Nov 2009) | 2 lines Fix typo. ................ r76535 | antoine.pitrou | 2009-11-26 13:36:30 +0100 (Do, 26 Nov 2009) | 3 lines When open_urlresource() fails, HTTPException is another possible error ................ r76546 | antoine.pitrou | 2009-11-27 14:18:34 +0100 (Fr, 27 Nov 2009) | 7 lines Issue #6845: Add restart support for binary upload in ftplib. The `storbinary()` method of FTP and FTP_TLS objects gains an optional `rest` argument. Patch by Pablo Mouzo. (note: the patch also adds a test for the rest argument in retrbinary()) ................ r76548 | antoine.pitrou | 2009-11-27 14:24:29 +0100 (Fr, 27 Nov 2009) | 3 lines Add ACKS entry for Pablo Mouzo ................ r76550 | martin.v.loewis | 2009-11-27 14:56:01 +0100 (Fr, 27 Nov 2009) | 2 lines Issue #6508: Add posix.{getresuid,getresgid,setresuid,setresgid}. ................ r76551 | vinay.sajip | 2009-11-27 15:03:36 +0100 (Fr, 27 Nov 2009) | 1 line Issue #7403: Fixed possible race condition in lock creation. ................ r76556 | gregory.p.smith | 2009-11-27 18:51:12 +0100 (Fr, 27 Nov 2009) | 2 lines fix typo ................ r76558 | mark.dickinson | 2009-11-28 11:44:20 +0100 (Sa, 28 Nov 2009) | 4 lines Issue #7272, continued: don't re-use existing HAVE_BROKEN_POSIX_SEMAPHORES to indicate that semaphores aren't available; define a new variable POSIX_SEMAPHORES_NOT_ENABLED instead. ................ r76561 | mark.dickinson | 2009-11-28 13:30:36 +0100 (Sa, 28 Nov 2009) | 5 lines Include ieeefp.h (when available) in pyport.h instead of individually in Objects/floatobject.c and Objects/complexobject.c. This should silence compiler warnings about implicit declaration of the 'finite' function on Solaris. ................ r76568 | mark.dickinson | 2009-11-28 14:13:13 +0100 (Sa, 28 Nov 2009) | 1 line Multiprocessing configure checks don't need LIBM ................ r76571 | antoine.pitrou | 2009-11-28 16:55:58 +0100 (Sa, 28 Nov 2009) | 3 lines Issue #1515: Enable use of deepcopy() with instance methods. Patch by Robert Collins. ................ r76583 | eric.smith | 2009-11-29 18:40:57 +0100 (So, 29 Nov 2009) | 1 line Issue #3382: Make '%F' and float.__format__('F') convert results to upper case. Much of the patch came from Mark Dickinson. ................ r76588 | tarek.ziade | 2009-11-29 23:20:30 +0100 (So, 29 Nov 2009) | 1 line Fixed #7408: dropped group ownership checking because it relies on os-specific rules ................ r76591 | benjamin.peterson | 2009-11-29 23:26:26 +0100 (So, 29 Nov 2009) | 4 lines now that deepcopy can handle instance methods, this hack can be removed #7409 Thanks Robert Collins ................ r76600 | raymond.hettinger | 2009-11-30 20:44:40 +0100 (Mo, 30 Nov 2009) | 3 lines Issue 7410: deepcopy of itertools.count resets the count ................ r76602 | raymond.hettinger | 2009-11-30 22:13:52 +0100 (Mo, 30 Nov 2009) | 1 line Handle step values other than one. ................ r76603 | raymond.hettinger | 2009-11-30 22:14:25 +0100 (Mo, 30 Nov 2009) | 1 line Update project file for new file: dtoa.c ................ r76605 | mark.dickinson | 2009-11-30 22:51:30 +0100 (Mo, 30 Nov 2009) | 2 lines Add dtoa.c and dtoa.h to the relevant project files. ................ r76623 | ronald.oussoren | 2009-12-01 16:54:01 +0100 (Di, 01 Dez 2009) | 9 lines Fix for issue #7416: SIZEOF_UINTPTR_T can be invalid when configuring a multi-architecture build (in particular when the architectures don't share a common pointer size). Fixed the same issue for SIZEOF_PTHREAD_T. (No update to the NEWS file because this is a bugfix for an as yet unreleased feature) ................ r76625 | amaury.forgeotdarc | 2009-12-01 22:51:04 +0100 (Di, 01 Dez 2009) | 3 lines #7419: Fix a crash on Windows in locale.setlocale() when the category is outside the allowed range. ................ r76628 | andrew.kuchling | 2009-12-02 15:27:11 +0100 (Mi, 02 Dez 2009) | 1 line Markup fixes ................ r76632 | eric.smith | 2009-12-02 18:43:06 +0100 (Mi, 02 Dez 2009) | 1 line Issue #4482: Add tests for special float value formatting. ................ r76636 | antoine.pitrou | 2009-12-02 21:37:54 +0100 (Mi, 02 Dez 2009) | 5 lines Issue #7333: The `posix` module gains an `initgroups()` function providing access to the initgroups(3) C library call on Unix systems which implement it. Patch by Jean-Paul Calderone. ................ r76640 | philip.jenvey | 2009-12-03 03:25:54 +0100 (Do, 03 Dez 2009) | 2 lines #7177: clarify the potential PIPE deadlock warnings ................ r76642 | philip.jenvey | 2009-12-03 03:40:13 +0100 (Do, 03 Dez 2009) | 1 line actually close files ................ r76644 | benjamin.peterson | 2009-12-03 03:52:39 +0100 (Do, 03 Dez 2009) | 4 lines disable pymalloc tricks with the --with-valgrind option #2422 Patch from James Henstridge. ................ r76648 | mark.dickinson | 2009-12-03 13:08:56 +0100 (Do, 03 Dez 2009) | 3 lines Issue #6985: number of range() items should be constrained to lie in a Py_ssize_t, not an int. ................ r76655 | martin.v.loewis | 2009-12-03 22:01:16 +0100 (Do, 03 Dez 2009) | 2 lines Add Christoph Gohlke, for the issue 4120 work. ................ r76668 | mark.dickinson | 2009-12-04 12:30:16 +0100 (Fr, 04 Dez 2009) | 1 line Add missing issue number in Misc/NEWS entry. ................ r76672 | benjamin.peterson | 2009-12-05 18:45:40 +0100 (Sa, 05 Dez 2009) | 1 line regenerate pydoc_topics ................ r76673 | benjamin.peterson | 2009-12-05 18:46:33 +0100 (Sa, 05 Dez 2009) | 2 lines move RPM spec for 2.7 ................ r76674 | benjamin.peterson | 2009-12-05 18:47:56 +0100 (Sa, 05 Dez 2009) | 1 line bump version to 2.7a1 ................ r76676 | benjamin.peterson | 2009-12-05 19:40:02 +0100 (Sa, 05 Dez 2009) | 1 line post release version bump ................ r76679 | benjamin.peterson | 2009-12-05 19:48:13 +0100 (Sa, 05 Dez 2009) | 1 line fix date ................ r76689 | benjamin.peterson | 2009-12-06 18:37:48 +0100 (So, 06 Dez 2009) | 1 line rewrite translate_newlines for clarity ................ r76690 | vinay.sajip | 2009-12-06 18:57:11 +0100 (So, 06 Dez 2009) | 1 line logging: Added optional 'secure' parameter to SMTPHandler. ................ r76691 | vinay.sajip | 2009-12-06 19:05:04 +0100 (So, 06 Dez 2009) | 1 line logging: Improved support for SMTP over TLS. ................ r76692 | martin.v.loewis | 2009-12-06 19:27:29 +0100 (So, 06 Dez 2009) | 2 lines Add UUIDs for 2.7. Drop UUIDs for 2.4. ................ r76697 | benjamin.peterson | 2009-12-06 22:24:30 +0100 (So, 06 Dez 2009) | 2 lines fix test_parser from tokenizer tweak ................ r76701 | andrew.kuchling | 2009-12-08 03:37:05 +0100 (Di, 08 Dez 2009) | 1 line Typo fix; grammar fix ................ r76702 | tarek.ziade | 2009-12-08 09:56:49 +0100 (Di, 08 Dez 2009) | 1 line Issue #7457: added a read_pkg_file method to distutils.dist.DistributionMetadata so we can read back PKG-INFO files ................ r76704 | tarek.ziade | 2009-12-08 10:39:51 +0100 (Di, 08 Dez 2009) | 1 line removed the usage of rfc822 in favor of email.message.Message ................ r76708 | antoine.pitrou | 2009-12-08 16:40:51 +0100 (Di, 08 Dez 2009) | 4 lines Issue #6986: Fix crash in the JSON C accelerator when called with the wrong parameter types. Patch by Victor Stinner. ................ r76712 | ronald.oussoren | 2009-12-08 17:32:52 +0100 (Di, 08 Dez 2009) | 4 lines Fix for issue 7452: HAVE_GCC_ASM_FOR_X87 gets set when doing a universal build on an i386 based machine, but should only be active when compiling the x86 part of the universal binary. ................ r76716 | antoine.pitrou | 2009-12-08 20:25:51 +0100 (Di, 08 Dez 2009) | 4 lines Fix the transient refleaks in test_zipimport_support. Diagnosis and original patch by Florent Xicluna (flox). ................ r76718 | antoine.pitrou | 2009-12-08 20:35:12 +0100 (Di, 08 Dez 2009) | 3 lines Fix transient refleaks in test_urllib. Thanks to Florent Xicluna. ................ r76720 | antoine.pitrou | 2009-12-08 20:46:38 +0100 (Di, 08 Dez 2009) | 3 lines Make test_pipes a little bit more robust. ................ r76733 | benjamin.peterson | 2009-12-10 04:37:59 +0100 (Do, 10 Dez 2009) | 1 line substitute PyDict_Check() for PyObject_IsInstance ................ r76736 | raymond.hettinger | 2009-12-10 07:00:33 +0100 (Do, 10 Dez 2009) | 1 line Fix variants of deque.extend: d.extend(d) d+=d d.extendleft(d) ................ r76737 | raymond.hettinger | 2009-12-10 07:42:54 +0100 (Do, 10 Dez 2009) | 1 line Add a reverse() method to collections.deque(). ................ r76740 | mark.dickinson | 2009-12-10 11:36:32 +0100 (Do, 10 Dez 2009) | 8 lines Replace the size check for PyMem_MALLOC and PyMem_REALLOC with an almost equivalent[*] check that doesn't produce compiler warnings about a 'x < 0' check on an unsigned type. [*] it's equivalent for inputs of type size_t or Py_ssize_t, or any smaller unsigned or signed integer type. ................ r76746 | tarek.ziade | 2009-12-10 16:29:03 +0100 (Do, 10 Dez 2009) | 1 line added test coverage for distutils.dep_util, and cleaned up the module ................ r76750 | tarek.ziade | 2009-12-10 20:29:53 +0100 (Do, 10 Dez 2009) | 1 line using an existing file to avoid dealing with a sleep to test file ages ................ r76754 | vinay.sajip | 2009-12-11 10:16:01 +0100 (Fr, 11 Dez 2009) | 1 line Issue #7470: logging: fix bug in Unicode encoding fallback. ................ r76755 | mark.dickinson | 2009-12-11 18:29:33 +0100 (Fr, 11 Dez 2009) | 2 lines Issue #3366: Add lgamma function to math module. ................ r76763 | antoine.pitrou | 2009-12-12 20:13:08 +0100 (Sa, 12 Dez 2009) | 7 lines Issue #7466: segmentation fault when the garbage collector is called in the middle of populating a tuple. Patch by Florent Xicluna. (note: no NEWS entry for trunk since the bug was introduced in 2.7/3.1) ................ r76780 | lars.gustaebel | 2009-12-13 12:32:27 +0100 (So, 13 Dez 2009) | 21 lines Issue #7357: No longer suppress fatal extraction errors by default. TarFile's errorlevel argument controls how errors are handled that occur during extraction. There are three possible levels 0, 1 and 2. If errorlevel is set to 1 or 2 fatal errors (e.g. a full filesystem) are raised as exceptions. If it is set to 0, which is the default value, extraction errors are suppressed, and error messages are written to the debug log instead. But, if the debug log is not activated, which is the default as well, all these errors go unnoticed. The original intention was to imitate GNU tar which tries to extract as many members as possible instead of stopping on the first error. It turns out that this is no good default behaviour for a tar library. This patch simply changes the default value for the errorlevel argument from 0 to 1, so that fatal extraction errors are raised as EnvironmentError exceptions. ................ r76791 | antoine.pitrou | 2009-12-13 17:18:14 +0100 (So, 13 Dez 2009) | 5 lines Add NEWS entry as per RDM's suggestion (the bug was actually present in 2.7 alpha 1) ................ r76805 | benjamin.peterson | 2009-12-13 20:19:07 +0100 (So, 13 Dez 2009) | 7 lines accept None as the same as having passed no argument in file types #7349 This is for consistency with imitation file objects like StringIO and BytesIO. This commit also adds a few tests, where they were lacking for concerned methods. ................ r76807 | benjamin.peterson | 2009-12-13 20:27:02 +0100 (So, 13 Dez 2009) | 1 line remove unused variable ................ r76813 | mark.dickinson | 2009-12-13 22:06:06 +0100 (So, 13 Dez 2009) | 3 lines Issue #7492: Autoconf tests were leaving semaphore files behind. Add sem_unlink calls to delete those semaphore files. ................ r76822 | benjamin.peterson | 2009-12-13 22:21:43 +0100 (So, 13 Dez 2009) | 1 line initialize to NULL ................ r76824 | benjamin.peterson | 2009-12-13 22:27:53 +0100 (So, 13 Dez 2009) | 1 line add a test of loading the datetime capi ................ r76826 | tarek.ziade | 2009-12-14 00:24:13 +0100 (Mo, 14 Dez 2009) | 1 line reorganized the distutils doc a bit : the MANIFEST.in template system has its own section now. This is easier to find and follow ................ r76831 | r.david.murray | 2009-12-14 17:28:26 +0100 (Mo, 14 Dez 2009) | 6 lines Issue #1680159: unicode coercion during an 'in' operation was masking any errors that might occur during coercion of the left operand and turning them into a TypeError with a message text that was confusing in the given context. This patch lets any errors through, as was already done during coercion of the right hand side. ................ r76849 | tarek.ziade | 2009-12-15 07:29:19 +0100 (Di, 15 Dez 2009) | 1 line cleaned up the module (PEP 8 + old fashion test removal) ................ r76851 | benjamin.peterson | 2009-12-16 04:28:52 +0100 (Mi, 16 Dez 2009) | 1 line remove lib2to3 resource ................ r76856 | r.david.murray | 2009-12-16 12:49:46 +0100 (Mi, 16 Dez 2009) | 2 lines Issue #7396: fix -s, which was broken by the -j enhancement. ................ r76861 | mark.dickinson | 2009-12-16 21:13:40 +0100 (Mi, 16 Dez 2009) | 3 lines Issue #3366: Add expm1 function to math module. Thanks Eric Smith for testing on Windows. ................ r76865 | mark.dickinson | 2009-12-17 09:33:56 +0100 (Do, 17 Dez 2009) | 1 line Add _math.h to math module dependencies in setup.py. ................ r76869 | vinay.sajip | 2009-12-17 15:52:00 +0100 (Do, 17 Dez 2009) | 1 line Issue #7529: logging: Minor correction to documentation. ................ r76878 | mark.dickinson | 2009-12-19 12:07:23 +0100 (Sa, 19 Dez 2009) | 3 lines Issue #3366: Add error function and complementary error function to math module. ................ r76898 | antoine.pitrou | 2009-12-19 22:06:36 +0100 (Sa, 19 Dez 2009) | 3 lines Remove superfetatory paragraph (left there by mistake). ................ r76912 | senthil.kumaran | 2009-12-20 08:29:31 +0100 (So, 20 Dez 2009) | 3 lines Document the headers parameter for set_tunnel. ................ r76916 | mark.dickinson | 2009-12-20 14:58:18 +0100 (So, 20 Dez 2009) | 3 lines math.factorial depends on PyLong_AsLong correctly converting floats; rewrite it to do the conversion explicitly instead. See issue #7550. ................ r76930 | mark.dickinson | 2009-12-20 16:57:56 +0100 (So, 20 Dez 2009) | 1 line Add missing tests for PyArg_Parse* with format 'h' ................ r76934 | r.david.murray | 2009-12-20 17:24:46 +0100 (So, 20 Dez 2009) | 2 lines Fix comment typo. ................ r76935 | r.david.murray | 2009-12-20 17:46:06 +0100 (So, 20 Dez 2009) | 10 lines Issue #7376: When called with no arguments doctest was running a self-test. Because of a change to the way tracebacks are printed, this self-test was failing. The test is run (and passes) during normal regression testing. So instead of running the failing self-test this patch makes doctest emit a usage message. This is better behavior anyway since passing in arguments is the real reason to run doctest as a command. Bug discovery and initial patch by Florent Xicluna. ................ r76948 | mark.dickinson | 2009-12-20 21:34:44 +0100 (So, 20 Dez 2009) | 3 lines Issue #7554: Various fixups in test_cmath.py: remove code duplication, use new-style formatting. Thanks Florent Xicluna for the patch. ................ r76956 | tarek.ziade | 2009-12-21 02:22:46 +0100 (Mo, 21 Dez 2009) | 1 line massive import cleaning in Distutils ................ r76963 | mark.dickinson | 2009-12-21 12:21:25 +0100 (Mo, 21 Dez 2009) | 3 lines Issue #7528: Backport PyLong_AsLongAndOverflow from py3k to trunk. Thanks Case Van Horsen for the patch. ................ r76967 | mark.dickinson | 2009-12-21 12:31:54 +0100 (Mo, 21 Dez 2009) | 1 line Fix reference counts for test_long_and_overflow. ................ r76968 | mark.dickinson | 2009-12-21 13:15:48 +0100 (Mo, 21 Dez 2009) | 1 line Additional edge-case tests for test_long_and_overflow. ................ r76973 | r.david.murray | 2009-12-21 13:45:41 +0100 (Mo, 21 Dez 2009) | 2 lines Remove a leftover from a previous iteration of the issue 7376 patch. ................ r76978 | mark.dickinson | 2009-12-21 16:22:00 +0100 (Mo, 21 Dez 2009) | 3 lines Issue #7518: Move substitute definitions of C99 math functions from pymath.c to Modules/_math.c. ................ r76982 | mark.dickinson | 2009-12-21 16:40:33 +0100 (Mo, 21 Dez 2009) | 2 lines Inverse hyperbolic trigonometric functions should call m_log1p, not log1p. ................ r76984 | mark.dickinson | 2009-12-21 17:29:21 +0100 (Mo, 21 Dez 2009) | 3 lines Issue #7553: test_long_future wasn't testing properly. Thanks Florent Xicluna for bug report and patch. ................ r76989 | martin.v.loewis | 2009-12-21 20:25:56 +0100 (Mo, 21 Dez 2009) | 1 line Drop 2.4 compatibility. ................ r76996 | tarek.ziade | 2009-12-22 00:31:55 +0100 (Di, 22 Dez 2009) | 1 line backported r76993 and r76994 so the trunk behaves the same way with MSVC Manifest files editing ................ r76998 | tarek.ziade | 2009-12-22 00:37:44 +0100 (Di, 22 Dez 2009) | 1 line added a note about #7556 in Misc/NEWS ................ |
||
---|---|---|
Demo | ||
Doc | ||
Grammar | ||
Include | ||
Lib | ||
Mac | ||
Misc | ||
Modules | ||
Objects | ||
PC | ||
PCbuild | ||
Parser | ||
Python | ||
RISCOS | ||
Tools | ||
.bzrignore | ||
.hgignore | ||
.hgtags | ||
LICENSE | ||
Makefile.pre.in | ||
README | ||
configure | ||
configure.in | ||
install-sh | ||
pyconfig.h.in | ||
setup.py |
README
This is Python version 2.6.5 ============================ Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Python Software Foundation. All rights reserved. Copyright (c) 2000 BeOpen.com. All rights reserved. Copyright (c) 1995-2001 Corporation for National Research Initiatives. All rights reserved. Copyright (c) 1991-1995 Stichting Mathematisch Centrum. All rights reserved. License information ------------------- See the file "LICENSE" for information on the history of this software, terms & conditions for usage, and a DISCLAIMER OF ALL WARRANTIES. This Python distribution contains no GNU General Public Licensed (GPLed) code so it may be used in proprietary projects just like prior Python distributions. There are interfaces to some GNU code but these are entirely optional. All trademarks referenced herein are property of their respective holders. What's new in this release? --------------------------- See the file "Misc/NEWS". If you don't read instructions ------------------------------ Congratulations on getting this far. :-) To start building right away (on UNIX): type "./configure" in the current directory and when it finishes, type "make". This creates an executable "./python"; to install in /usr/local, first do "su root" and then "make install". The section `Build instructions' below is still recommended reading. What is Python anyway? ---------------------- Python is an interpreted, interactive object-oriented programming language suitable (amongst other uses) for distributed application development, scripting, numeric computing and system testing. Python is often compared to Tcl, Perl, Java, JavaScript, Visual Basic or Scheme. To find out more about what Python can do for you, point your browser to http://www.python.org/. How do I learn Python? ---------------------- The official tutorial is still a good place to start; see http://docs.python.org/ for online and downloadable versions, as well as a list of other introductions, and reference documentation. There's a quickly growing set of books on Python. See http://wiki.python.org/moin/PythonBooks for a list. Documentation ------------- All documentation is provided online in a variety of formats. In order of importance for new users: Tutorial, Library Reference, Language Reference, Extending & Embedding, and the Python/C API. The Library Reference is especially of immense value since much of Python's power is described there, including the built-in data types and functions! All documentation is also available online at the Python web site (http://docs.python.org/, see below). It is available online for occasional reference, or can be downloaded in many formats for faster access. The documentation is downloadable in HTML, PostScript, PDF, LaTeX, and reStructuredText (2.6+) formats; the LaTeX and reStructuredText versions are primarily for documentation authors, translators, and people with special formatting requirements. Web sites --------- New Python releases and related technologies are published at http://www.python.org/. Come visit us! Newsgroups and Mailing Lists ---------------------------- Read comp.lang.python, a high-volume discussion newsgroup about Python, or comp.lang.python.announce, a low-volume moderated newsgroup for Python-related announcements. These are also accessible as mailing lists: see http://www.python.org/community/lists/ for an overview of these and many other Python-related mailing lists. Archives are accessible via the Google Groups Usenet archive; see http://groups.google.com/. The mailing lists are also archived, see http://www.python.org/community/lists/ for details. Bug reports ----------- To report or search for bugs, please use the Python Bug Tracker at http://bugs.python.org/. Patches and contributions ------------------------- To submit a patch or other contribution, please use the Python Patch Manager at http://bugs.python.org/. Guidelines for patch submission may be found at http://www.python.org/dev/patches/. If you have a proposal to change Python, you may want to send an email to the comp.lang.python or python-ideas mailing lists for inital feedback. A Python Enhancement Proposal (PEP) may be submitted if your idea gains ground. All current PEPs, as well as guidelines for submitting a new PEP, are listed at http://www.python.org/dev/peps/. Questions --------- For help, if you can't find it in the manuals or on the web site, it's best to post to the comp.lang.python or the Python mailing list (see above). If you specifically don't want to involve the newsgroup or mailing list, send questions to help@python.org (a group of volunteers who answer questions as they can). The newsgroup is the most efficient way to ask public questions. Build instructions ================== Before you can build Python, you must first configure it. Fortunately, the configuration and build process has been automated for Unix and Linux installations, so all you usually have to do is type a few commands and sit back. There are some platforms where things are not quite as smooth; see the platform specific notes below. If you want to build for multiple platforms sharing the same source tree, see the section on VPATH below. Start by running the script "./configure", which determines your system configuration and creates the Makefile. (It takes a minute or two -- please be patient!) You may want to pass options to the configure script -- see the section below on configuration options and variables. When it's done, you are ready to run make. To build Python, you normally type "make" in the toplevel directory. If you have changed the configuration, the Makefile may have to be rebuilt. In this case, you may have to run make again to correctly build your desired target. The interpreter executable is built in the top level directory. Once you have built a Python interpreter, see the subsections below on testing and installation. If you run into trouble, see the next section. Previous versions of Python used a manual configuration process that involved editing the file Modules/Setup. While this file still exists and manual configuration is still supported, it is rarely needed any more: almost all modules are automatically built as appropriate under guidance of the setup.py script, which is run by Make after the interpreter has been built. Troubleshooting --------------- See also the platform specific notes in the next section. If you run into other trouble, see the FAQ (http://www.python.org/doc/faq/) for hints on what can go wrong, and how to fix it. If you rerun the configure script with different options, remove all object files by running "make clean" before rebuilding. Believe it or not, "make clean" sometimes helps to clean up other inexplicable problems as well. Try it before sending in a bug report! If the configure script fails or doesn't seem to find things that should be there, inspect the config.log file. If you get a warning for every file about the -Olimit option being no longer supported, you can ignore it. There's no foolproof way to know whether this option is needed; all we can do is test whether it is accepted without error. On some systems, e.g. older SGI compilers, it is essential for performance (specifically when compiling ceval.c, which has more basic blocks than the default limit of 1000). If the warning bothers you, edit the Makefile to remove "-Olimit 1500" from the OPT variable. If you get failures in test_long, or sys.maxint gets set to -1, you are probably experiencing compiler bugs, usually related to optimization. This is a common problem with some versions of gcc, and some vendor-supplied compilers, which can sometimes be worked around by turning off optimization. Consider switching to stable versions (gcc 2.95.2, gcc 3.x, or contact your vendor.) From Python 2.0 onward, all Python C code is ANSI C. Compiling using old K&R-C-only compilers is no longer possible. ANSI C compilers are available for all modern systems, either in the form of updated compilers from the vendor, or one of the free compilers (gcc). If "make install" fails mysteriously during the "compiling the library" step, make sure that you don't have any of the PYTHONPATH or PYTHONHOME environment variables set, as they may interfere with the newly built executable which is compiling the library. Unsupported systems ------------------- A number of features are not supported in Python 2.5 anymore. Some support code is still present, but will be removed in Python 2.6. If you still need to use current Python versions on these systems, please send a message to python-dev@python.org indicating that you volunteer to support this system. For a more detailed discussion regarding no-longer-supported and resupporting platforms, as well as a list of platforms that became or will be unsupported, see PEP 11. More specifically, the following systems are not supported any longer: - SunOS 4 - DYNIX - dgux - Minix - NeXT - Irix 4 and --with-sgi-dl - Linux 1 - Systems defining __d6_pthread_create (configure.in) - Systems defining PY_PTHREAD_D4, PY_PTHREAD_D6, or PY_PTHREAD_D7 in thread_pthread.h - Systems using --with-dl-dld - Systems using --without-universal-newlines - MacOS 9 The following systems are still supported in Python 2.5, but support will be dropped in 2.6: - Systems using --with-wctype-functions - Win9x, WinME Warning on install in Windows 98 and Windows Me ----------------------------------------------- Following Microsoft's closing of Extended Support for Windows 98/ME (July 11, 2006), Python 2.6 will stop supporting these platforms. Python development and maintainability becomes easier (and more reliable) when platform specific code targeting OSes with few users and no dedicated expert developers is taken out. The vendor also warns that the OS versions listed above "can expose customers to security risks" and recommends upgrade. Platform specific notes ----------------------- (Some of these may no longer apply. If you find you can build Python on these platforms without the special directions mentioned here, submit a documentation bug report to SourceForge (see Bug Reports above) so we can remove them!) Unix platforms: If your vendor still ships (and you still use) Berkeley DB 1.85 you will need to edit Modules/Setup to build the bsddb185 module and add a line to sitecustomize.py which makes it the default. In Modules/Setup a line like bsddb185 bsddbmodule.c should work. (You may need to add -I, -L or -l flags to direct the compiler and linker to your include files and libraries.) XXX I think this next bit is out of date: 64-bit platforms: The modules audioop, and imageop don't work. The setup.py script disables them on 64-bit installations. Don't try to enable them in the Modules/Setup file. They contain code that is quite wordsize sensitive. (If you have a fix, let us know!) Solaris: When using Sun's C compiler with threads, at least on Solaris 2.5.1, you need to add the "-mt" compiler option (the simplest way is probably to specify the compiler with this option as the "CC" environment variable when running the configure script). When using GCC on Solaris, beware of binutils 2.13 or GCC versions built using it. This mistakenly enables the -zcombreloc option which creates broken shared libraries on Solaris. binutils 2.12 works, and the binutils maintainers are aware of the problem. Binutils 2.13.1 only partially fixed things. It appears that 2.13.2 solves the problem completely. This problem is known to occur with Solaris 2.7 and 2.8, but may also affect earlier and later versions of the OS. When the dynamic loader complains about errors finding shared libraries, such as ld.so.1: ./python: fatal: libstdc++.so.5: open failed: No such file or directory you need to first make sure that the library is available on your system. Then, you need to instruct the dynamic loader how to find it. You can choose any of the following strategies: 1. When compiling Python, set LD_RUN_PATH to the directories containing missing libraries. 2. When running Python, set LD_LIBRARY_PATH to these directories. 3. Use crle(8) to extend the search path of the loader. 4. Modify the installed GCC specs file, adding -R options into the *link: section. The complex object fails to compile on Solaris 10 with gcc 3.4 (at least up to 3.4.3). To work around it, define Py_HUGE_VAL as HUGE_VAL(), e.g.: make CPPFLAGS='-D"Py_HUGE_VAL=HUGE_VAL()" -I. -I$(srcdir)/Include' ./python setup.py CPPFLAGS='-D"Py_HUGE_VAL=HUGE_VAL()"' Linux: A problem with threads and fork() was tracked down to a bug in the pthreads code in glibc version 2.0.5; glibc version 2.0.7 solves the problem. This causes the popen2 test to fail; problem and solution reported by Pablo Bleyer. Red Hat Linux: Red Hat 9 built Python2.2 in UCS-4 mode and hacked Tcl to support it. To compile Python2.3 with Tkinter, you will need to pass --enable-unicode=ucs4 flag to ./configure. There's an executable /usr/bin/python which is Python 1.5.2 on most older Red Hat installations; several key Red Hat tools require this version. Python 2.1.x may be installed as /usr/bin/python2. The Makefile installs Python as /usr/local/bin/python, which may or may not take precedence over /usr/bin/python, depending on how you have set up $PATH. FreeBSD 3.x and probably platforms with NCurses that use libmytinfo or similar: When using cursesmodule, the linking is not done in the correct order with the defaults. Remove "-ltermcap" from the readline entry in Setup, and use as curses entry: "curses cursesmodule.c -lmytinfo -lncurses -ltermcap" - "mytinfo" (so called on FreeBSD) should be the name of the auxiliary library required on your platform. Normally, it would be linked automatically, but not necessarily in the correct order. BSDI: BSDI versions before 4.1 have known problems with threads, which can cause strange errors in a number of modules (for instance, the 'test_signal' test script will hang forever.) Turning off threads (with --with-threads=no) or upgrading to BSDI 4.1 solves this problem. DEC Unix: Run configure with --with-dec-threads, or with --with-threads=no if no threads are desired (threads are on by default). When using GCC, it is possible to get an internal compiler error if optimization is used. This was reported for GCC 2.7.2.3 on selectmodule.c. Manually compile the affected file without optimization to solve the problem. DEC Ultrix: compile with GCC to avoid bugs in the native compiler, and pass SHELL=/bin/sh5 to Make when installing. AIX: A complete overhaul of the shared library support is now in place. See Misc/AIX-NOTES for some notes on how it's done. (The optimizer bug reported at this place in previous releases has been worked around by a minimal code change.) If you get errors about pthread_* functions, during compile or during testing, try setting CC to a thread-safe (reentrant) compiler, like "cc_r". For full C++ module support, set CC="xlC_r" (or CC="xlC" without thread support). AIX 5.3: To build a 64-bit version with IBM's compiler, I used the following: export PATH=/usr/bin:/usr/vacpp/bin ./configure --with-gcc="xlc_r -q64" --with-cxx="xlC_r -q64" \ --disable-ipv6 AR="ar -X64" make HP-UX: When using threading, you may have to add -D_REENTRANT to the OPT variable in the top-level Makefile; reported by Pat Knight, this seems to make a difference (at least for HP-UX 10.20) even though pyconfig.h defines it. This seems unnecessary when using HP/UX 11 and later - threading seems to work "out of the box". HP-UX ia64: When building on the ia64 (Itanium) platform using HP's compiler, some experience has shown that the compiler's optimiser produces a completely broken version of python (see http://bugs.python.org/814976). To work around this, edit the Makefile and remove -O from the OPT line. To build a 64-bit executable on an Itanium 2 system using HP's compiler, use these environment variables: CC=cc CXX=aCC BASECFLAGS="+DD64" LDFLAGS="+DD64 -lxnet" and call configure as: ./configure --without-gcc then *unset* the environment variables again before running make. (At least one of these flags causes the build to fail if it remains set.) You still have to edit the Makefile and remove -O from the OPT line. HP PA-RISC 2.0: A recent bug report (http://bugs.python.org/546117) suggests that the C compiler in this 64-bit system has bugs in the optimizer that break Python. Compiling without optimization solves the problems. SCO: The following apply to SCO 3 only; Python builds out of the box on SCO 5 (or so we've heard). 1) Everything works much better if you add -U__STDC__ to the defs. This is because all the SCO header files are broken. Anything that isn't mentioned in the C standard is conditionally excluded when __STDC__ is defined. 2) Due to the U.S. export restrictions, SCO broke the crypt stuff out into a separate library, libcrypt_i.a so the LIBS needed be set to: LIBS=' -lsocket -lcrypt_i' UnixWare: There are known bugs in the math library of the system, as well as problems in the handling of threads (calling fork in one thread may interrupt system calls in others). Therefore, test_math and tests involving threads will fail until those problems are fixed. QNX: Chris Herborth (chrish@qnx.com) writes: configure works best if you use GNU bash; a port is available on ftp.qnx.com in /usr/free. I used the following process to build, test and install Python 1.5.x under QNX: 1) CONFIG_SHELL=/usr/local/bin/bash CC=cc RANLIB=: \ ./configure --verbose --without-gcc --with-libm="" 2) edit Modules/Setup to activate everything that makes sense for your system... tested here at QNX with the following modules: array, audioop, binascii, cPickle, cStringIO, cmath, crypt, curses, errno, fcntl, gdbm, grp, imageop, _locale, math, md5, new, operator, parser, pcre, posix, pwd, readline, regex, reop, select, signal, socket, soundex, strop, struct, syslog, termios, time, timing, zlib, audioop, imageop 3) make SHELL=/usr/local/bin/bash or, if you feel the need for speed: make SHELL=/usr/local/bin/bash OPT="-5 -Oil+nrt" 4) make SHELL=/usr/local/bin/bash test Using GNU readline 2.2 seems to behave strangely, but I think that's a problem with my readline 2.2 port. :-\ 5) make SHELL=/usr/local/bin/bash install If you get SIGSEGVs while running Python (I haven't yet, but I've only run small programs and the test cases), you're probably running out of stack; the default 32k could be a little tight. To increase the stack size, edit the Makefile to read: LDFLAGS = -N 48k BeOS: See Misc/BeOS-NOTES for notes about compiling/installing Python on BeOS R3 or later. Note that only the PowerPC platform is supported for R3; both PowerPC and x86 are supported for R4. Cray T3E: Mark Hadfield (m.hadfield@niwa.co.nz) writes: Python can be built satisfactorily on a Cray T3E but based on my experience with the NIWA T3E (2002-05-22, version 2.2.1) there are a few bugs and gotchas. For more information see a thread on comp.lang.python in May 2002 entitled "Building Python on Cray T3E". 1) Use Cray's cc and not gcc. The latter was reported not to work by Konrad Hinsen. It may work now, but it may not. 2) To set sys.platform to something sensible, pass the following environment variable to the configure script: MACHDEP=unicosmk 2) Run configure with option "--enable-unicode=ucs4". 3) The Cray T3E does not support dynamic linking, so extension modules have to be built by adding (or uncommenting) lines in Modules/Setup. The minimum set of modules is posix, new, _sre, unicodedata On NIWA's vanilla T3E system the following have also been included successfully: _codecs, _locale, _socket, _symtable, _testcapi, _weakref array, binascii, cmath, cPickle, crypt, cStringIO, dbm errno, fcntl, grp, math, md5, operator, parser, pcre, pwd regex, rotor, select, struct, strop, syslog, termios time, timing, xreadlines 4) Once the python executable and library have been built, make will execute setup.py, which will attempt to build remaining extensions and link them dynamically. Each of these attempts will fail but should not halt the make process. This is normal. 5) Running "make test" uses a lot of resources and causes problems on our system. You might want to try running tests singly or in small groups. SGI: SGI's standard "make" utility (/bin/make or /usr/bin/make) does not check whether a command actually changed the file it is supposed to build. This means that whenever you say "make" it will redo the link step. The remedy is to use SGI's much smarter "smake" utility (/usr/sbin/smake), or GNU make. If you set the first line of the Makefile to #!/usr/sbin/smake smake will be invoked by make (likewise for GNU make). WARNING: There are bugs in the optimizer of some versions of SGI's compilers that can cause bus errors or other strange behavior, especially on numerical operations. To avoid this, try building with "make OPT=". OS/2: If you are running Warp3 or Warp4 and have IBM's VisualAge C/C++ compiler installed, just change into the pc\os2vacpp directory and type NMAKE. Threading and sockets are supported by default in the resulting binaries of PYTHON15.DLL and PYTHON.EXE. Monterey (64-bit AIX): The current Monterey C compiler (Visual Age) uses the OBJECT_MODE={32|64} environment variable to set the compilation mode to either 32-bit or 64-bit (32-bit mode is the default). Presumably you want 64-bit compilation mode for this 64-bit OS. As a result you must first set OBJECT_MODE=64 in your environment before configuring (./configure) or building (make) Python on Monterey. Reliant UNIX: The thread support does not compile on Reliant UNIX, and there is a (minor) problem in the configure script for that platform as well. This should be resolved in time for a future release. MacOSX: The tests will crash on both 10.1 and 10.2 with SEGV in test_re and test_sre due to the small default stack size. If you set the stack size to 2048 before doing a "make test" the failure can be avoided. If you're using the tcsh or csh shells, use "limit stacksize 2048" and for the bash shell (the default as of OSX 10.3), use "ulimit -s 2048". On naked Darwin you may want to add the configure option "--disable-toolbox-glue" to disable the glue code for the Carbon interface modules. The modules themselves are currently only built if you add the --enable-framework option, see below. On a clean OSX /usr/local does not exist. Do a "sudo mkdir -m 775 /usr/local" before you do a make install. It is probably not a good idea to do "sudo make install" which installs everything as superuser, as this may later cause problems when installing distutils-based additions. Some people have reported problems building Python after using "fink" to install additional unix software. Disabling fink (remove all references to /sw from your .profile or .login) should solve this. You may want to try the configure option "--enable-framework" which installs Python as a framework. The location can be set as argument to the --enable-framework option (default /Library/Frameworks). A framework install is probably needed if you want to use any Aqua-based GUI toolkit (whether Tkinter, wxPython, Carbon, Cocoa or anything else). You may also want to try the configure option "--enable-universalsdk" which builds Python as a universal binary with support for the i386 and PPC architetures. This requires Xcode 2.1 or later to build. See Mac/README for more information on framework and universal builds. Cygwin: With recent (relative to the time of writing, 2001-12-19) Cygwin installations, there are problems with the interaction of dynamic linking and fork(). This manifests itself in build failures during the execution of setup.py. There are two workarounds that both enable Python (albeit without threading support) to build and pass all tests on NT/2000 (and most likely XP as well, though reports of testing on XP would be appreciated). The workarounds: (a) the band-aid fix is to link the _socket module statically rather than dynamically (which is the default). To do this, run "./configure --with-threads=no" including any other options you need (--prefix, etc.). Then in Modules/Setup uncomment the lines: #SSL=/usr/local/ssl #_socket socketmodule.c \ # -DUSE_SSL -I$(SSL)/include -I$(SSL)/include/openssl \ # -L$(SSL)/lib -lssl -lcrypto and remove "local/" from the SSL variable. Finally, just run "make"! (b) The "proper" fix is to rebase the Cygwin DLLs to prevent base address conflicts. Details on how to do this can be found in the following mail: http://sources.redhat.com/ml/cygwin/2001-12/msg00894.html It is hoped that a version of this solution will be incorporated into the Cygwin distribution fairly soon. Two additional problems: (1) Threading support should still be disabled due to a known bug in Cygwin pthreads that causes test_threadedtempfile to hang. (2) The _curses module does not build. This is a known Cygwin ncurses problem that should be resolved the next time that this package is released. On older versions of Cygwin, test_poll may hang and test_strftime may fail. The situation on 9X/Me is not accurately known at present. Some time ago, there were reports that the following regression tests failed: test_pwd test_select (hang) test_socket Due to the test_select hang on 9X/Me, one should run the regression test using the following: make TESTOPTS='-l -x test_select' test News regarding these platforms with more recent Cygwin versions would be appreciated! Windows: When executing Python scripts on the command line using file type associations (i.e. starting "script.py" instead of "python script.py"), redirects may not work unless you set a specific registry key. See the Knowledge Base article <http://support.microsoft.com/kb/321788>. Configuring the bsddb and dbm modules ------------------------------------- Beginning with Python version 2.3, the PyBsddb package <http://pybsddb.sf.net/> was adopted into Python as the bsddb package, exposing a set of package-level functions which provide backwards-compatible behavior. Only versions 3.3 through 4.4 of Sleepycat's libraries provide the necessary API, so older versions aren't supported through this interface. The old bsddb module has been retained as bsddb185, though it is not built by default. Users wishing to use it will have to tweak Modules/Setup to build it. The dbm module will still be built against the Sleepycat libraries if other preferred alternatives (ndbm, gdbm) are not found. Building the sqlite3 module --------------------------- To build the sqlite3 module, you'll need the sqlite3 or libsqlite3 packages installed, including the header files. Many modern operating systems distribute the headers in a separate package to the library - often it will be the same name as the main package, but with a -dev or -devel suffix. The version of pysqlite2 that's including in Python needs sqlite3 3.0.8 or later. setup.py attempts to check that it can find a correct version. Configuring threads ------------------- As of Python 2.0, threads are enabled by default. If you wish to compile without threads, or if your thread support is broken, pass the --with-threads=no switch to configure. Unfortunately, on some platforms, additional compiler and/or linker options are required for threads to work properly. Below is a table of those options, collected by Bill Janssen. We would love to automate this process more, but the information below is not enough to write a patch for the configure.in file, so manual intervention is required. If you patch the configure.in file and are confident that the patch works, please send in the patch. (Don't bother patching the configure script itself -- it is regenerated each time the configure.in file changes.) Compiler switches for threads ............................. The definition of _REENTRANT should be configured automatically, if that does not work on your system, or if _REENTRANT is defined incorrectly, please report that as a bug. OS/Compiler/threads Switches for use with threads (POSIX is draft 10, DCE is draft 4) compile & link SunOS 5.{1-5}/{gcc,SunPro cc}/solaris -mt SunOS 5.5/{gcc,SunPro cc}/POSIX (nothing) DEC OSF/1 3.x/cc/DCE -threads (butenhof@zko.dec.com) Digital UNIX 4.x/cc/DCE -threads (butenhof@zko.dec.com) Digital UNIX 4.x/cc/POSIX -pthread (butenhof@zko.dec.com) AIX 4.1.4/cc_r/d7 (nothing) (buhrt@iquest.net) AIX 4.1.4/cc_r4/DCE (nothing) (buhrt@iquest.net) IRIX 6.2/cc/POSIX (nothing) (robertl@cwi.nl) Linker (ld) libraries and flags for threads ........................................... OS/threads Libraries/switches for use with threads SunOS 5.{1-5}/solaris -lthread SunOS 5.5/POSIX -lpthread DEC OSF/1 3.x/DCE -lpthreads -lmach -lc_r -lc (butenhof@zko.dec.com) Digital UNIX 4.x/DCE -lpthreads -lpthread -lmach -lexc -lc (butenhof@zko.dec.com) Digital UNIX 4.x/POSIX -lpthread -lmach -lexc -lc (butenhof@zko.dec.com) AIX 4.1.4/{draft7,DCE} (nothing) (buhrt@iquest.net) IRIX 6.2/POSIX -lpthread (jph@emilia.engr.sgi.com) Building a shared libpython --------------------------- Starting with Python 2.3, the majority of the interpreter can be built into a shared library, which can then be used by the interpreter executable, and by applications embedding Python. To enable this feature, configure with --enable-shared. If you enable this feature, the same object files will be used to create a static library. In particular, the static library will contain object files using position-independent code (PIC) on platforms where PIC flags are needed for the shared library. Configuring additional built-in modules --------------------------------------- Starting with Python 2.1, the setup.py script at the top of the source distribution attempts to detect which modules can be built and automatically compiles them. Autodetection doesn't always work, so you can still customize the configuration by editing the Modules/Setup file; but this should be considered a last resort. The rest of this section only applies if you decide to edit the Modules/Setup file. You also need this to enable static linking of certain modules (which is needed to enable profiling on some systems). This file is initially copied from Setup.dist by the configure script; if it does not exist yet, create it by copying Modules/Setup.dist yourself (configure will never overwrite it). Never edit Setup.dist -- always edit Setup or Setup.local (see below). Read the comments in the file for information on what kind of edits are allowed. When you have edited Setup in the Modules directory, the interpreter will automatically be rebuilt the next time you run make (in the toplevel directory). Many useful modules can be built on any Unix system, but some optional modules can't be reliably autodetected. Often the quickest way to determine whether a particular module works or not is to see if it will build: enable it in Setup, then if you get compilation or link errors, disable it -- you're either missing support or need to adjust the compilation and linking parameters for that module. On SGI IRIX, there are modules that interface to many SGI specific system libraries, e.g. the GL library and the audio hardware. These modules will not be built by the setup.py script. In addition to the file Setup, you can also edit the file Setup.local. (the makesetup script processes both). You may find it more convenient to edit Setup.local and leave Setup alone. Then, when installing a new Python version, you can copy your old Setup.local file. Setting the optimization/debugging options ------------------------------------------ If you want or need to change the optimization/debugging options for the C compiler, assign to the OPT variable on the toplevel make command; e.g. "make OPT=-g" will build a debugging version of Python on most platforms. The default is OPT=-O; a value for OPT in the environment when the configure script is run overrides this default (likewise for CC; and the initial value for LIBS is used as the base set of libraries to link with). When compiling with GCC, the default value of OPT will also include the -Wall and -Wstrict-prototypes options. Additional debugging code to help debug memory management problems can be enabled by using the --with-pydebug option to the configure script. For flags that change binary compatibility, use the EXTRA_CFLAGS variable. Profiling --------- If you want C profiling turned on, the easiest way is to run configure with the CC environment variable to the necessary compiler invocation. For example, on Linux, this works for profiling using gprof(1): CC="gcc -pg" ./configure Note that on Linux, gprof apparently does not work for shared libraries. The Makefile/Setup mechanism can be used to compile and link most extension modules statically. Coverage checking ----------------- For C coverage checking using gcov, run "make coverage". This will build a Python binary with profiling activated, and a ".gcno" and ".gcda" file for every source file compiled with that option. With the built binary, now run the code whose coverage you want to check. Then, you can see coverage statistics for each individual source file by running gcov, e.g. gcov -o Modules zlibmodule This will create a "zlibmodule.c.gcov" file in the current directory containing coverage info for that source file. This works only for source files statically compiled into the executable; use the Makefile/Setup mechanism to compile and link extension modules you want to coverage-check statically. Testing ------- To test the interpreter, type "make test" in the top-level directory. This runs the test set twice (once with no compiled files, once with the compiled files left by the previous test run). The test set produces some output. You can generally ignore the messages about skipped tests due to optional features which can't be imported. If a message is printed about a failed test or a traceback or core dump is produced, something is wrong. On some Linux systems (those that are not yet using glibc 6), test_strftime fails due to a non-standard implementation of strftime() in the C library. Please ignore this, or upgrade to glibc version 6. By default, tests are prevented from overusing resources like disk space and memory. To enable these tests, run "make testall". IMPORTANT: If the tests fail and you decide to mail a bug report, *don't* include the output of "make test". It is useless. Run the failing test manually, as follows: ./python Lib/test/regrtest.py -v test_whatever (substituting the top of the source tree for '.' if you built in a different directory). This runs the test in verbose mode. Installing ---------- To install the Python binary, library modules, shared library modules (see below), include files, configuration files, and the manual page, just type make install This will install all platform-independent files in subdirectories of the directory given with the --prefix option to configure or to the `prefix' Make variable (default /usr/local). All binary and other platform-specific files will be installed in subdirectories if the directory given by --exec-prefix or the `exec_prefix' Make variable (defaults to the --prefix directory) is given. If DESTDIR is set, it will be taken as the root directory of the installation, and files will be installed into $(DESTDIR)$(prefix), $(DESTDIR)$(exec_prefix), etc. All subdirectories created will have Python's version number in their name, e.g. the library modules are installed in "/usr/local/lib/python<version>/" by default, where <version> is the <major>.<minor> release number (e.g. "2.1"). The Python binary is installed as "python<version>" and a hard link named "python" is created. The only file not installed with a version number in its name is the manual page, installed as "/usr/local/man/man1/python.1" by default. If you want to install multiple versions of Python see the section below entitled "Installing multiple versions". The only thing you may have to install manually is the Python mode for Emacs found in Misc/python-mode.el. (But then again, more recent versions of Emacs may already have it.) Follow the instructions that came with Emacs for installation of site-specific files. On Mac OS X, if you have configured Python with --enable-framework, you should use "make frameworkinstall" to do the installation. Note that this installs the Python executable in a place that is not normally on your PATH, you may want to set up a symlink in /usr/local/bin. Installing multiple versions ---------------------------- On Unix and Mac systems if you intend to install multiple versions of Python using the same installation prefix (--prefix argument to the configure script) you must take care that your primary python executable is not overwritten by the installation of a different version. All files and directories installed using "make altinstall" contain the major and minor version and can thus live side-by-side. "make install" also creates ${prefix}/bin/python which refers to ${prefix}/bin/pythonX.Y. If you intend to install multiple versions using the same prefix you must decide which version (if any) is your "primary" version. Install that version using "make install". Install all other versions using "make altinstall". For example, if you want to install Python 2.5, 2.6 and 3.0 with 2.6 being the primary version, you would execute "make install" in your 2.6 build directory and "make altinstall" in the others. Configuration options and variables ----------------------------------- Some special cases are handled by passing options to the configure script. WARNING: if you rerun the configure script with different options, you must run "make clean" before rebuilding. Exceptions to this rule: after changing --prefix or --exec-prefix, all you need to do is remove Modules/getpath.o. --with(out)-gcc: The configure script uses gcc (the GNU C compiler) if it finds it. If you don't want this, or if this compiler is installed but broken on your platform, pass the option --without-gcc. You can also pass "CC=cc" (or whatever the name of the proper C compiler is) in the environment, but the advantage of using --without-gcc is that this option is remembered by the config.status script for its --recheck option. --prefix, --exec-prefix: If you want to install the binaries and the Python library somewhere else than in /usr/local/{bin,lib}, you can pass the option --prefix=DIRECTORY; the interpreter binary will be installed as DIRECTORY/bin/python and the library files as DIRECTORY/lib/python/*. If you pass --exec-prefix=DIRECTORY (as well) this overrides the installation prefix for architecture-dependent files (like the interpreter binary). Note that --prefix=DIRECTORY also affects the default module search path (sys.path), when Modules/config.c is compiled. Passing make the option prefix=DIRECTORY (and/or exec_prefix=DIRECTORY) overrides the prefix set at configuration time; this may be more convenient than re-running the configure script if you change your mind about the install prefix. --with-readline: This option is no longer supported. GNU readline is automatically enabled by setup.py when present. --with-threads: On most Unix systems, you can now use multiple threads, and support for this is enabled by default. To disable this, pass --with-threads=no. If the library required for threads lives in a peculiar place, you can use --with-thread=DIRECTORY. IMPORTANT: run "make clean" after changing (either enabling or disabling) this option, or you will get link errors! Note: for DEC Unix use --with-dec-threads instead. --with-sgi-dl: On SGI IRIX 4, dynamic loading of extension modules is supported by the "dl" library by Jack Jansen, which is ftp'able from ftp://ftp.cwi.nl/pub/dynload/dl-1.6.tar.Z. This is enabled (after you've ftp'ed and compiled the dl library) by passing --with-sgi-dl=DIRECTORY where DIRECTORY is the absolute pathname of the dl library. (Don't bother on IRIX 5, it already has dynamic linking using SunOS style shared libraries.) THIS OPTION IS UNSUPPORTED. --with-dl-dld: Dynamic loading of modules is rumored to be supported on some other systems: VAX (Ultrix), Sun3 (SunOS 3.4), Sequent Symmetry (Dynix), and Atari ST. This is done using a combination of the GNU dynamic loading package (ftp://ftp.cwi.nl/pub/dynload/dl-dld-1.1.tar.Z) and an emulation of the SGI dl library mentioned above (the emulation can be found at ftp://ftp.cwi.nl/pub/dynload/dld-3.2.3.tar.Z). To enable this, ftp and compile both libraries, then call configure, passing it the option --with-dl-dld=DL_DIRECTORY,DLD_DIRECTORY where DL_DIRECTORY is the absolute pathname of the dl emulation library and DLD_DIRECTORY is the absolute pathname of the GNU dld library. (Don't bother on SunOS 4 or 5, they already have dynamic linking using shared libraries.) THIS OPTION IS UNSUPPORTED. --with-libm, --with-libc: It is possible to specify alternative versions for the Math library (default -lm) and the C library (default the empty string) using the options --with-libm=STRING and --with-libc=STRING, respectively. For example, if your system requires that you pass -lc_s to the C compiler to use the shared C library, you can pass --with-libc=-lc_s. These libraries are passed after all other libraries, the C library last. --with-libs='libs': Add 'libs' to the LIBS that the python interpreter is linked against. --with-cxx-main=<compiler>: If you plan to use C++ extension modules, then -- on some platforms -- you need to compile python's main() function with the C++ compiler. With this option, make will use <compiler> to compile main() *and* to link the python executable. It is likely that the resulting executable depends on the C++ runtime library of <compiler>. (The default is --without-cxx-main.) There are platforms that do not require you to build Python with a C++ compiler in order to use C++ extension modules. E.g., x86 Linux with ELF shared binaries and GCC 3.x, 4.x is such a platform. We recommend that you configure Python --without-cxx-main on those platforms because a mismatch between the C++ compiler version used to build Python and to build a C++ extension module is likely to cause a crash at runtime. The Python installation also stores the variable CXX that determines, e.g., the C++ compiler distutils calls by default to build C++ extensions. If you set CXX on the configure command line to any string of non-zero length, then configure won't change CXX. If you do not preset CXX but pass --with-cxx-main=<compiler>, then configure sets CXX=<compiler>. In all other cases, configure looks for a C++ compiler by some common names (c++, g++, gcc, CC, cxx, cc++, cl) and sets CXX to the first compiler it finds. If it does not find any C++ compiler, then it sets CXX="". Similarly, if you want to change the command used to link the python executable, then set LINKCC on the configure command line. --with-pydebug: Enable additional debugging code to help track down memory management problems. This allows printing a list of all live objects when the interpreter terminates. --with(out)-universal-newlines: enable reading of text files with foreign newline convention (default: enabled). In other words, any of \r, \n or \r\n is acceptable as end-of-line character. If enabled import and execfile will automatically accept any newline in files. Python code can open a file with open(file, 'U') to read it in universal newline mode. THIS OPTION IS UNSUPPORTED. --with-tsc: Profile using the Pentium timestamping counter (TSC). --with-system-ffi: Build the _ctypes extension module using an ffi library installed on the system. Building for multiple architectures (using the VPATH feature) ------------------------------------------------------------- If your file system is shared between multiple architectures, it usually is not necessary to make copies of the sources for each architecture you want to support. If the make program supports the VPATH feature, you can create an empty build directory for each architecture, and in each directory run the configure script (on the appropriate machine with the appropriate options). This creates the necessary subdirectories and the Makefiles therein. The Makefiles contain a line VPATH=... which points to a directory containing the actual sources. (On SGI systems, use "smake -J1" instead of "make" if you use VPATH -- don't try gnumake.) For example, the following is all you need to build a minimal Python in /usr/tmp/python (assuming ~guido/src/python is the toplevel directory and you want to build in /usr/tmp/python): $ mkdir /usr/tmp/python $ cd /usr/tmp/python $ ~guido/src/python/configure [...] $ make [...] $ Note that configure copies the original Setup file to the build directory if it finds no Setup file there. This means that you can edit the Setup file for each architecture independently. For this reason, subsequent changes to the original Setup file are not tracked automatically, as they might overwrite local changes. To force a copy of a changed original Setup file, delete the target Setup file. (The makesetup script supports multiple input files, so if you want to be fancy you can change the rules to create an empty Setup.local if it doesn't exist and run it with arguments $(srcdir)/Setup Setup.local; however this assumes that you only need to add modules.) Also note that you can't use a workspace for VPATH and non VPATH builds. The object files left behind by one version confuses the other. Building on non-UNIX systems ---------------------------- For Windows (2000/NT/ME/98/95), assuming you have MS VC++ 7.1, the project files are in PCbuild, the workspace is pcbuild.dsw. See PCbuild\readme.txt for detailed instructions. For other non-Unix Windows compilers, in particular MS VC++ 6.0 and for OS/2, enter the directory "PC" and read the file "readme.txt". For the Mac, a separate source distribution will be made available, for use with the CodeWarrior compiler. If you are interested in Mac development, join the PythonMac Special Interest Group (http://www.python.org/sigs/pythonmac-sig/, or send email to pythonmac-sig-request@python.org). Of course, there are also binary distributions available for these platforms -- see http://www.python.org/. To port Python to a new non-UNIX system, you will have to fake the effect of running the configure script manually (for Mac and PC, this has already been done for you). A good start is to copy the file pyconfig.h.in to pyconfig.h and edit the latter to reflect the actual configuration of your system. Most symbols must simply be defined as 1 only if the corresponding feature is present and can be left alone otherwise; however the *_t type symbols must be defined as some variant of int if they need to be defined at all. For all platforms, it's important that the build arrange to define the preprocessor symbol NDEBUG on the compiler command line in a release build of Python (else assert() calls remain in the code, hurting release-build performance). The Unix, Windows and Mac builds already do this. Miscellaneous issues ==================== Emacs mode ---------- There's an excellent Emacs editing mode for Python code; see the file Misc/python-mode.el. Originally written by the famous Tim Peters, it is now maintained by the equally famous Barry Warsaw (it's no coincidence that they now both work on the same team). The latest version, along with various other contributed Python-related Emacs goodies, is online at http://www.python.org/emacs/python-mode/. And if you are planning to edit the Python C code, please pick up the latest version of CC Mode http://www.python.org/emacs/cc-mode/; it contains a "python" style used throughout most of the Python C source files. (Newer versions of Emacs or XEmacs may already come with the latest version of python-mode.) Tkinter ------- The setup.py script automatically configures this when it detects a usable Tcl/Tk installation. This requires Tcl/Tk version 8.0 or higher. For more Tkinter information, see the Tkinter Resource page: http://www.python.org/topics/tkinter/ There are demos in the Demo/tkinter directory. Note that there's a Python module called "Tkinter" (capital T) which lives in Lib/lib-tk/Tkinter.py, and a C module called "_tkinter" (lower case t and leading underscore) which lives in Modules/_tkinter.c. Demos and normal Tk applications import only the Python Tkinter module -- only the latter imports the C _tkinter module. In order to find the C _tkinter module, it must be compiled and linked into the Python interpreter -- the setup.py script does this. In order to find the Python Tkinter module, sys.path must be set correctly -- normal installation takes care of this. Distribution structure ---------------------- Most subdirectories have their own README files. Most files have comments. Demo/ Demonstration scripts, modules and programs Doc/ Documentation sources (reStructuredText) Grammar/ Input for the parser generator Include/ Public header files LICENSE Licensing information Lib/ Python library modules Mac/ Macintosh specific resources Makefile.pre.in Source from which config.status creates the Makefile.pre Misc/ Miscellaneous useful files Modules/ Implementation of most built-in modules Objects/ Implementation of most built-in object types PC/ Files specific to PC ports (DOS, Windows, OS/2) PCbuild/ Build directory for Microsoft Visual C++ Parser/ The parser and tokenizer and their input handling Python/ The byte-compiler and interpreter README The file you're reading now RISCOS/ Files specific to RISC OS port Tools/ Some useful programs written in Python pyconfig.h.in Source from which pyconfig.h is created (GNU autoheader output) configure Configuration shell script (GNU autoconf output) configure.in Configuration specification (input for GNU autoconf) install-sh Shell script used to install files setup.py Python script used to build extension modules The following files will (may) be created in the toplevel directory by the configuration and build processes: Makefile Build rules Makefile.pre Build rules before running Modules/makesetup buildno Keeps track of the build number config.cache Cache of configuration variables pyconfig.h Configuration header config.log Log from last configure run config.status Status from last run of the configure script getbuildinfo.o Object file from Modules/getbuildinfo.c libpython<version>.a The library archive python The executable interpreter reflog.txt Output from running the regression suite with the -R flag tags, TAGS Tags files for vi and Emacs That's all, folks! ------------------ --Guido van Rossum (home page: http://www.python.org/~guido/)