Mailman 3 August 2006 - Python-Dev

free(): invalid pointer
by Ralf Schmitt 08 Aug '06

08 Aug '06

Hi all, I've got another error porting our apps. It's a django app and stops with (when pressing CTRL-C): *** glibc detected *** free(): invalid pointer: 0xb684c650 *** with MALLOC_CHECK=1 and gdb I get the following backtrace: Program received signal SIGINT, Interrupt. [Switching to Thread -1209690432 (LWP 10036)] 0xffffe410 in __kernel_vsyscall () (gdb) *** glibc detected *** free(): invalid pointer: 0xb66a22a8 *** (gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0xb7fbd463 in __waitpid_nocancel () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x080ed524 in posix_waitpid (self=0x0, args=0xfffffe00) at ./Modules/posixmodule.c:5502 #3 0x080bec34 in PyEval_EvalFrameEx (f=0x825a3b4, throwflag=0) at Python/ceval.c:3565 #4 0x080be459 in PyEval_EvalFrameEx (f=0x81bd60c, throwflag=0) at Python/ceval.c:3650 #5 0x080be459 in PyEval_EvalFrameEx (f=0x82354f4, throwflag=0) at Python/ceval.c:3650 #6 0x080be459 in PyEval_EvalFrameEx (f=0x81dbb94, throwflag=0) at Python/ceval.c:3650 #7 0x080bff75 in PyEval_EvalCodeEx (co=0xb7c91c38, globals=0xb7a3713c, locals=0x0, args=0x822fcd0, argcount=1, kws=0x822fcd4, kwcount=0, defs=0xb7a33058, defcount=2, closure=0x0) at Python/ceval.c:2832 #8 0x080bd771 in PyEval_EvalFrameEx (f=0x822fb6c, throwflag=0) at Python/ceval.c:3661 #9 0x080bff75 in PyEval_EvalCodeEx (co=0xb7dfeba8, globals=0xb7dfd714, locals=0x0, args=0x820165c, argcount=2, kws=0x8201664, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:2832 #10 0x080bd771 in PyEval_EvalFrameEx (f=0x82014cc, throwflag=0) at Python/ceval.c:3661 #11 0x080bff75 in PyEval_EvalCodeEx (co=0xb7dfede8, globals=0xb7dfd714, locals=0x0, args=0x81ec784, argcount=1, kws=0x81ec788, kwcount=0, defs=0xb7cfcdb8, defcount=1, closure=0x0) at Python/ceval.c:2832 #12 0x080bd771 in PyEval_EvalFrameEx (f=0x81ec634, throwflag=0) at Python/ceval.c:3661 #13 0x080be459 in PyEval_EvalFrameEx (f=0x81ae054, throwflag=0) at Python/ceval.c:3650 #14 0x080bff75 in PyEval_EvalCodeEx (co=0xb7de2770, globals=0xb7e319bc, locals=0xb7e319bc, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:2832 ---Type <return> to continue, or q <return> to quit--- #15 0x080c00f6 in PyEval_EvalCode (co=0xfffffe00, globals=0xfffffe00, locals=0xfffffe00) at Python/ceval.c:494 #16 0x080de682 in PyRun_FileExFlags (fp=0x815f008, filename=0xbfdf18b1 "manage.py", start=-512, globals=0xfffffe00, locals=0xfffffe00, closeit=1, flags=0xbfdefbb8) at Python/pythonrun.c:1255 #17 0x080de9f3 in PyRun_SimpleFileExFlags (fp=<value optimized out>, filename=0xbfdf18b1 "manage.py", closeit=1, flags=0xbfdefbb8) at Python/pythonrun.c:861 #18 0x08056a69 in Py_Main (argc=2, argv=0xbfdefc54) at Modules/main.c:496 #19 0xb7e6fea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #20 0x08055fa1 in _start () at ../sysdeps/i386/elf/start.S:119 I'm using Python 2.5b3 (trunk:51066M, Aug 3 2006, 16:55:04). Sorry for not using the bugtracker (sf sucks). Did you guys already settle on a new one? - Ralf

1 1

windows 2.5 build: use OpenSSL for hashlib [bug 1535502]
by Gregory P. Smith 08 Aug '06

08 Aug '06

Whoever knows how the windows build process works and controls the python 2.5 windows release builds could you please make sure the hashlib module gets built + linked with OpenSSL rather than falling back to its much slower builtin implementations. http://sourceforge.net/tracker/index.php?func=detail&aid=1535502&group_id=5… thanks, greg

3 11

Four issue trackers submitted for Infrastructue Committee's tracker search
by Brett Cannon 08 Aug '06

08 Aug '06

Back in June, the Python Software Foundation's Infrastructure Committee asked for help in the search for a new issue tracker to replace SourceForge (see http://wiki.python.org/moin/CallForTrackers for details). We asked people who wished to help with the search to install their favourite issue tracker and import a data dump of our issues from SourceForge. We placed a deadline of August 7th to have the installation up and going. We realized that this was a large request to make of the community, but we needed to make sure that we got to evaluate any candidate trackers with the amount of issues that Python has so as to get a real-world feel. Not surprisingly, the community stepped up to the challenge with four different test tracker installations by the deadline! We have one for JIRA, Roundup, Trac, and Launchpad. The current schedule calls for the Infrastructure Committee to spend the next month evaluating the four trackers and making a decision on which one to go with. This might slip, though, since this overlaps with traditional American and European vacation time. But the slippage will not go beyond October 1. On behalf of the Infrastructure committee I thank the people who took the time and effort to set up a test tracker to help improve the development of Python. - Brett Cannon Chairman, PSF Infrastructure Committee

1 0

Python 2.5b3 and AIX 4.3 - It Works
by Michael Kent 07 Aug '06

07 Aug '06

Because of a requirement to remain compatible with AIX 4.3, I have been forced to stay with Python 2.3, because while 2.4 would compile under AIX 4.3, it would segfault immediately when run. I'm happy to report that Python 2.5b3 compiles and runs fine under AIX 4.3, and passes most of its test suite. However, here are a few test failures. I realize AIX 4.3 is long obsolete, so is there any interest on the list for me to report which tests failed and how?

3 2

cgi.FieldStorage DOS (sf bug #1112549)
by Chris McDonough 07 Aug '06

07 Aug '06

From the initial bugreport (http://sourceforge.net/tracker/index.php? func=detail&aid=1112549&group_id=5470&atid=105470) """ Various parts of cgi.FieldStorage call its "read_lines_to_outerboundary", "read_lines" and "skip_lines" methods. These methods use the "readline" method of the file object that represents an input stream. The input stream is typically data supplied by an untrusted source (such as a user uploading a file from a web browser). The input data is not required by the RFC 822/1521/1522/1867 specifications to contain any newline characters. For example, it is within the bounds of the specification to supply a a multipart/form-data input stream with a "file-data" part that consists of a 2GB string composed entirely of "x" characters (which happens to be something I did that led me to noticing this bug). """ This bug has been around for about a year but I just worked up a patch yesterday that applies OK against current SVN. It's attached to the issue. Would someone be so kind as to check it in? Guido has already reviewed it, I believe. - C

2 1

Re: [Python-Dev] More tracker demos online
by Hernan M Foffani 06 Aug '06

06 Aug '06

> > > > Currently, we have two running tracker demos online: > > > > > > > > Roundup: > > > > http://efod.se/python-tracker/ > > > > > > > > Jira: > > > > http://jira.python.atlassian.com/secure/Dashboard.jspa > > > Is anyone looking at the Google Code Hosting tracker, just for fun? =) ( > code.google.com/hosting, although performance seems to be an issue for now) It's propietary code, isn't it? http://code.google.com/hosting/faq.html#itselfoss (Is that why you said "just for fun"?) Regards, -H.

3 2

BZ2File.writelines should raise more meaningful exceptions
by Lawrence Oluyede 06 Aug '06

06 Aug '06

In the BZ2File object of bz2 module the writelines() method does not check its closed state before doing the actual work so its behavior it's different from write()'s behavior. See: >>> from bz2 import BZ2File >>> f = BZ2File("foo", "w") >>> f.close() >>> f.closed 1 >>> f.write("foobar") Traceback (most recent call last): File "<stdin>", line 1, in <module> ValueError: I/O operation on closed file >>> f.closed 1 >>> f.writelines(["foobar"]) Traceback (most recent call last): File "<stdin>", line 1, in <module> IOError: unknown IO error It also doesn't check if it can write for real: >>> from bz2 import BZ2File >>> f = BZ2File("foo", "r") >>> f.write("foobar") Traceback (most recent call last): File "<stdin>", line 1, in <module> IOError: file is not ready for writing >>> f.writelines(['foobar']) Traceback (most recent call last): File "<stdin>", line 1, in <module> RuntimeError: wrong sequence of bz2 library commands used The patch is attached. If you think it's ok to fix this I'll post it to the bug tracker -- Lawrence http://www.oluyede.org/blog

2 2

test_mailbox on Cygwin
by Andrew MacIntyre 06 Aug '06

06 Aug '06

I just had a look at the Cygwin buildbot's test log, and noticed that test_mailbox has failures that look very similar to those I addressed in rev 50789 for the OS/2 EMX platform. Hopefully this might give someone with access to Cygwin a starting point in getting this test working on that platform. -- ------------------------------------------------------------------------- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac(a)bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac(a)pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia

1 0

need an SSH key removed
by Brett Cannon 05 Aug '06

05 Aug '06

My bcannon(a)google.com SSH key should be removed since my internship is now over. -Brett

3 2

More tracker demos online
by "Martin v. Löwis" 04 Aug '06

04 Aug '06

Currently, we have two running tracker demos online: Roundup: http://efod.se/python-tracker/ Jira: http://jira.python.atlassian.com/secure/Dashboard.jspa These installation are in various forms of demo mode and "pre-release" (meaning that the configuration is still not complete). They both use the sample data that Fredrik Lundh produced at some point, so don't be surprised that they are behind SF wrt. content. While these might not be in the final form of operation, I think users should already try to use them, to find out which one they like best. Discussions/Comments can be sent to infrastructure(a)python.org, however, for reports/reviews, please use the Wiki at http://wiki.python.org/moin/CallForTrackers You'll notice that it also lists Trac and Malone, however, it seems that there is no progress on importing SF data into these. Regards, Martin

7 8