<h3>Bugs in Python 2.3.1</h3>
<li>IDLE now executes code in a separate process. To communicate between the main process and executing processes, IDLE opens a socket to 127.0.0.1 (the local machine). Some firewalls running on Windows machines interfere with this and can cause either silent failures or erroneous popup windows from the firewall. This problem only occurs if you run a firewall on the same machine as IDLE.</li>
<li>The test for the ossaudiodev module hangs on some Red Hat systems. (This test is only run when regrtest.py is invoked with <code>-u audio</code> as argument.)</li>
<li>It has been reported that untarring the source tarball using Solaris tar can fail. This is caused by some pathnames being too long for Solaris tar to handle. Using <a href="http://www.gnu.org/software/tar/tar.html">GNU tar</a> should allow for untarring on Solaris.
<li>Building on HP/UX is problematic. You probably want to compile using "cc -Ae" or "gcc", but even then there's a bug in either autoconf or HP/UX that means most time-related functions will be undefined. For now, edit the pyconfig.h file after running configure and set the following to defined: <br> HAVE_CLOCK HAVE_GETTIMEOFDAY HAVE_MKTIME HAVE_SELECT HAVE_STRFTIME HAVE_STRPTIME HAVE_UTIMES.<br> This will be fixed in a future release of Python. See <a href="http://python.org/sf/811160">this bug</a> for more, including a possible fix. </li>
<li>A bug in the autoconfiguration script means that the 'fsync' function in the 'os' module is unavailable. This will be addressed in 2.3.2 - for now, edit the generated pyconfig.h (after configure has been run) and change the line #define HAVE_SYNC to #define HAVE_FSYNC </li>
<li>Some tests may unexpectedly fail on certain platforms. Here are failures that we know (something) about and intend to fix in a following patch release. These bugs may simply be in the test suite, but they may indicate bugs in Python.</li>
<li>test_grp and test_pwd may fail. We've had reports of this on *nix systems that use a "+" at the beginning of a line in the /etc/group or /etc/passwd file to indicate NIS/YP or LDAP consultation. The bugs may also be related to duplicate id in these files. See SourceForge bug reports number <a href="http://python.org/sf/775964">775964</a> and <a href="http://python.org/sf/779218">779218</a>.</li>
<li>There have been some reports on Debian systems about test_ioctl failures. We haven't be able to more widely reproduce this. See SourceForge bug report number <a href="http://python.org/sf/777867">777867</a></li>
<li>There have been reports that test_bsddb may fail on some systems. This appears to be a fault in the test suite - code using bsddb seems to be fine.
<li>test_tempfile and test_popen fail on Windows if Python is installed to a path with a space in the name. This failure is only in the test suite.
<li>test_tempfile may fail on HP/UX if your maximum number of filedescriptors is low (it appears to be 60 by default).
<li>When running the tests in random order (regrtest.py -r) test_mimetypes may fail. This is a fault in the test suite, the library code itself is fine.
<p>To report a bug not listed above, always check the SourceForge <a href="http://sourceforge.net/bugs/?group_id=5470">Bug Tracker</a> to see if they've already been reported. Use the bug tracker to report new bugs. If you have a patch, please use the SourceForge <a href="http://sourceforge.net/patch/?group_id=5470">Patch Manager</a>. Please mention that you are reporting a bug in 2.3, and note that you must have a SourceForge account and be logged in to submit a bug report or patch (we require this in case we need more information from you).</p>
<p>If you have access to an "unusual" platform, you might want to consider adding your report to the Wiki page <a href="http://wiki.python.org/moin/Python_202_2e3_2e1_20Platform_20Reports">Python 2.3.1 Platform Reports</a>.</p>