Notice: While Javascript is not essential for this website, your interaction with the content will be limited. Please turn Javascript on for the full experience.

Bugs in Python 2.3.2

<h3>Bugs in Python 2.3.2</h3>


<li>IDLE now executes code in a separate process. To communicate between the main process and executing processes, IDLE opens a socket to (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>


<a name="build"><h4>Build bugs</h4></a>

<p>Some platforms require some tinkering to get a clean build of Python. These bugs were all discovered at a point where it was too late to fit them into 2.3.2. They should hopefully be fixed in a 2.3.3 release.


<li>Some sort of weird dynamic linker error causes dbmmodule to fail on OSF/1 5.1, at least on the HP test machines.

<li>It has been reported that untarring the source tarball using Solaris tar or HP/UX tar can fail. This is caused by some pathnames being too long for the tar shipped by the vendor to handle. Using <a href="">GNU tar</a> should allow for untarring on Solaris and HP/UX.

<li>A bug in the /usr/include/ncurses.h header file on FreeBSD and MacOS X 10.2 means that the cursesmodule will fail to build. Edit the file and remove the line <pre>

AC_DEFINE(_XOPEN_SOURCE_EXTENDED, 1, Define to activate Unix95-and-earlier features)

</pre> and then run 'autoconf' to rebuild the configure file. This bug is fixed in OS X 10.3, and will hopefully be fixed in a future release of FreeBSD. If you don't have autoconf installed, a <a href="freebsd-curses.patch">patch</a> is available.

<li>A bug in SGI's header files means that socketmodule.c might fail to compile with an error about INET_ADDRSTRLEN. A <a href="sgi-socketmodule.patch">patch</a> for this is here.


<a name="test"><h4>Test suite bugs</h4></a>

<p>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>The test for the ossaudiodev module hangs on some Red Hat systems. (This test is only run when is invoked with <code>-u audio</code> as argument.)</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="">775964</a> and <a href="">779218</a>.</li>

System Message: WARNING/2 (<string>, line 62); backlink

Inline emphasis start-string without end-string.

<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="">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 ( -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="">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="">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="">Python 2.3.1 Platform Reports</a>.</p>