[issue9041] raised exception is misleading
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9041 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11860] reference 2.3 has text that runs past the page
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11860 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9896] Introspectable range objects
Daniel Urban urban.dani...@gmail.com added the comment: Now that the moratorium has already ended, I'll try again. I've updated the patch. It seems, that this idea has already came up in the past: Guido in msg70525 said: I also think ranges should be introspectable, exposing their start, stop and step values just like slice objects. A possible use case: the range slicing logic is quite complex (with a lot of corner cases). It would be good, if this logic would be accessible from Python code, for example to compute a slice of a slice-like-thing. Currently slicing a range object returns another range object, but there is no way to determine the bounds of this new object. -- versions: +Python 3.3 -Python 3.2 Added file: http://bugs.python.org/file21692/range_attrs_2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9896 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11861] 2to3 fails with a ParseError
New submission from Vinay Sajip vinay_sa...@yahoo.co.uk: 2to3 fails on boto/rds/__init__.py with a ParseError: vinay@eta-natty:~/tools/boto$ 2to3 boto/rds/__init__.py RefactoringTool: Skipping implicit fixer: buffer RefactoringTool: Skipping implicit fixer: idioms RefactoringTool: Skipping implicit fixer: set_literal RefactoringTool: Skipping implicit fixer: ws_comma RefactoringTool: Can't parse boto/rds/__init__.py: ParseError: bad input: type=1, value='RDSRegionInfo', context=('\n', (48, 12)) RefactoringTool: No files need to be modified. RefactoringTool: There was 1 error: RefactoringTool: Can't parse boto/rds/__init__.py: ParseError: bad input: type=1, value='RDSRegionInfo', context=('\n', (48, 12)) -- components: 2to3 (2.x to 3.0 conversion tool) files: __init__.py messages: 133922 nosy: vinay.sajip priority: normal severity: normal status: open title: 2to3 fails with a ParseError versions: Python 3.2, Python 3.3 Added file: http://bugs.python.org/file21693/__init__.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11861 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11859] test_interrupted_write_text() of test_io failed of Python 3.3 on FreeBSD 7.2
Antoine Pitrou pit...@free.fr added the comment: Agreed with your analysis. The problem is that the signal module doesn't expose pthread_sigmask. We could grab Jean-Paul's implementation from http://bazaar.launchpad.net/~exarkun/python-signalfd/trunk/view/head:/signalfd/_signalfd.c (although I'm not sure why the method is called sigprocmask while it calls pthread_sigmask). -- nosy: +exarkun ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11859 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11861] 2to3 fails with a ParseError
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +benjamin.peterson, ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11861 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11276] 2to3: imports fixer doesn't update references to modules specified without attributes
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment: Another example: when processing if hasattr(httplib, 'ssl'): pass It doesn't spot that httplib should be changed to http.client. -- nosy: +vinay.sajip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11276 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9762] PEP 3149 related build failures
Jan Groenewald jan.groenew...@gmail.com added the comment: I am trying to build www.sagemath.org on ubuntu 10.04 natty beta 2 for amd64. Bear with me. Sage includes a patched version of python2.6.4, and it fails to build modules nis and crypt. Upstream python 2.6.4, 2.6.6, and 2.7.1 fail to build with the same error with ./configure, make, as per the README. The patch proposed is for setup.py, which is not used here? Ubuntu has a packaged python 2.6.6 and 2.7.1 (default) which I assume is patched, and builds on their toolchain. -- nosy: +Jan.Groenewald versions: +Python 2.6 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9762 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9762] PEP 3149 related build failures
Jan Groenewald jan.groenew...@gmail.com added the comment: Oops, correction. Ubuntu 11.04 beta 2 for amd64. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9762 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10271] warnings.showwarning should allow any callable object
lekma lekma...@gmail.com added the comment: - split the patch between the actual fix and the test - rewrote the test a little bit (I'm not sure it's even needed, hence the split) - rediff against 3.3 (should still apply cleanly on top of 3.2 (modulo offset)) -- versions: +Python 3.3 Added file: http://bugs.python.org/file21694/Issue10271.33.fix.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10271 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10271] warnings.showwarning should allow any callable object
Changes by lekma lekma...@gmail.com: Added file: http://bugs.python.org/file21695/Issue10271.33.test.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10271 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9762] PEP 3149 related build failures
Barry A. Warsaw ba...@python.org added the comment: On Apr 17, 2011, at 01:46 PM, Jan Groenewald wrote: Jan Groenewald jan.groenew...@gmail.com added the comment: I am trying to build www.sagemath.org on ubuntu 10.04 natty beta 2 for amd64. Bear with me. As described in your follow up, the problem is really on 11.04. Sage includes a patched version of python2.6.4, and it fails to build modules nis and crypt. Upstream python 2.6.4, 2.6.6, and 2.7.1 fail to build with the same error with ./configure, make, as per the README. The patch proposed is for setup.py, which is not used here? Ubuntu has a packaged python 2.6.6 and 2.7.1 (default) which I assume is patched, and builds on their toolchain. This is not related to PEP 3149 failures. Ubuntu 11.04 introduced multiarch directories for the underlying shared libraries used to link to the Python extension modules. Unpatched, Python's setup.py does not add the necessary multiarch directories to the search paths, so some extensions won't build. Ubuntu 11.04's Python packages have been patched to add the correct search paths. Upstream Python 2.7, 3.1, 3.2, and 3.3 have also been patched to include the correct search paths, but fixed versions have not been released upstream yet. Python 2.6 won't be patched. See issue 11715 for details. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9762 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11849] ElementTree memory leak
Charles-Francois Natali neolo...@free.fr added the comment: The problem is not with Python, but with your libc. When a program - such as Python - returns memory, it uses the free(3) library call. But the libc is free to either return the memory immediately to the kernel using the relevant syscall (brk, munmap), or keep it around just in case (to simplify). It seems that RHEL5 and onwards tend to keep a lot of memory around, at least in this case (probably because of the allocation pattern). To sum up, python is returning memory, but your libc is not. You can force it using malloc_trim, see the attached patch (I'm not at all suggesting its inclusion, it's just an illustration). Results with current code: *** Python 3.3.0 alpha --- PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND 0 29823 pts/0S+ 0:00 1 1607 168176 8596 0.2 ./python /tmp/issue11849_test.py 1 29823 pts/0S+ 0:01 1 1607 249400 87088 2.2 ./python /tmp/issue11849_test.py 2 29823 pts/0S+ 0:03 1 1607 324080 161704 4.1 ./python /tmp/issue11849_test.py 3 29823 pts/0S+ 0:04 1 1607 398960 235036 5.9 ./python /tmp/issue11849_test.py 4 29823 pts/0S+ 0:06 1 1607 473356 309464 7.8 ./python /tmp/issue11849_test.py 5 29823 pts/0S+ 0:07 1 1607 548120 384624 9.8 ./python /tmp/issue11849_test.py 6 29823 pts/0S+ 0:09 1 1607 622884 458332 11.6 ./python /tmp/issue11849_test.py 7 29823 pts/0S+ 0:10 1 1607 701864 535736 13.6 ./python /tmp/issue11849_test.py 8 29823 pts/0S+ 0:12 1 1607 772440 607988 15.5 ./python /tmp/issue11849_test.py 9 29823 pts/0S+ 0:13 1 1607 851156 685384 17.4 ./python /tmp/issue11849_test.py END 29823 pts/0S+ 0:16 1 1607 761712 599400 15.2 ./python /tmp/issue11849_test.py GC 29823 pts/0S+ 0:16 1 1607 680900 519280 13.2 ./python /tmp/issue11849_test.py *** 29823 pts/0S+ 0:16 1 1607 680900 519288 13.2 ./python /tmp/issue11849_test.py Results with the malloc_trim: *** Python 3.3.0 alpha --- PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND 0 30020 pts/0S+ 0:00 1 1607 168180 8596 0.2 ./python /tmp/issue11849_test.py 1 30020 pts/0S+ 0:01 1 1607 249404 86160 2.1 ./python /tmp/issue11849_test.py 2 30020 pts/0S+ 0:03 1 1607 324084 160596 4.0 ./python /tmp/issue11849_test.py 3 30020 pts/0S+ 0:04 1 1607 398964 235036 5.9 ./python /tmp/issue11849_test.py 4 30020 pts/0S+ 0:06 1 1607 473360 309808 7.9 ./python /tmp/issue11849_test.py 5 30020 pts/0S+ 0:07 1 1607 548124 383896 9.7 ./python /tmp/issue11849_test.py 6 30020 pts/0S+ 0:09 1 1607 622888 458716 11.7 ./python /tmp/issue11849_test.py 7 30020 pts/0S+ 0:10 1 1607 701868 536124 13.6 ./python /tmp/issue11849_test.py 8 30020 pts/0S+ 0:12 1 1607 772444 607212 15.4 ./python /tmp/issue11849_test.py 9 30020 pts/0S+ 0:14 1 1607 851160 684608 17.4 ./python /tmp/issue11849_test.py END 30020 pts/0S+ 0:16 1 1607 761716 599524 15.3 ./python /tmp/issue11849_test.py GC 30020 pts/0S+ 0:16 1 1607 680776 10744 0.2 ./python /tmp/issue11849_test.py *** 30020 pts/0S+ 0:16 1 1607 680776 10752 0.2 ./python /tmp/issue11849_test.py -- nosy: +neologix ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11849 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11849] ElementTree memory leak
Changes by Charles-Francois Natali neolo...@free.fr: -- keywords: +patch Added file: http://bugs.python.org/file21696/gc_trim.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11849 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue828450] sdist generates bad MANIFEST on Windows
Changes by higery shoulderhig...@gmail.com: Removed file: http://bugs.python.org/file21691/change_path_separator_in_MANIFEST.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue828450 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue828450] sdist generates bad MANIFEST on Windows
Changes by higery shoulderhig...@gmail.com: Added file: http://bugs.python.org/file21697/change_path_separator_in_MANIFEST.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue828450 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11700] mailbox.py proxy updates
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment: On Sat, Apr 16, 2011 at 08:17:30PM +, R. David Murray wrote: [...] rather odd considering that there is also a 'closed' method that would fail similarly if close was ever called. Maybe someone got not enough feedback after she wrote the patch. (The only use for the existing 'closed' method that I can see is to see if somebody else closed the file out from under the ProxyFile, a 'feature' that seems of dubious utility.) After i've read io.rst - as above - i thought someone started to comply to one of the interfaces shown therein, went away because the current bug was fixed and there was no more time left at the moment to continue the work ... and actually never found back to do so. This really made sense to me because that actually happened a few days after i first got on the Internet to contact python.org. I would like to say that if someone reads file-like objects in io.rst and then also in mailbox.rst, and uses a box.get_file() returned object with that description in mind, there will be inconsistent failures. Steffen, [...] I plan to close this issue by applying my patch. That is a pity. But the main thing is that the bug gets fixed. - .closed is better than my version (talking about .sigh). - I would add a self.assertFalse(proxy.closed) test before the first .close(). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11700 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11700] mailbox.py proxy updates
R. David Murray rdmur...@bitdance.com added the comment: Ah. Well, since the io module and its classes didn't exist when that code in mailbox.py was written, no, that's not what happened :) Nor does 'file like object' in Python necessarily mean conformance to the io specification. We are *tending* in that direction, but the actual expected method set is really considerably smaller (and I'm not sure it is documented anywhere). I will incorporate your suggestion into the patch, thanks. Ezio also pointed out that I should be checking for the 'closed' method's existence before calling it, so I will add that as well. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11700 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5723] Incomplete json tests
Bob Ippolito b...@redivi.com added the comment: I did this some time ago in simplejson by defining a TestSuite subclass and instrumenting simplejson so that speedups can be enabled and disabled easily with a private API. https://github.com/simplejson/simplejson/blob/master/simplejson/tests/__init__.py -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5723 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10932] distutils.core.setup - data_files misbehaviour ?
Prashant Kumar contactprashan...@gmail.com added the comment: I made changes in manifest.py which can be viewed here: https://bitbucket.org/pkumar/distutils2_bugs/changeset/111c1253ea7a I'm not sure if I should modify test_command_sdist.py for the failing tests of manifest contents(since it is mentioned not to edit). msg133834: I don’t understand this comment: “Though, inside zip-file we get files without its parent dir, nothing changes in manifest file(should it change?) code from test_command_sdist.py: zip_file = zipfile.ZipFile(join(dist_folder, 'fake-1.0.zip')) try: content = zip_file.namelist() finally: zip_file.close() after the change as mentioned in msg127191, the value of content changed, i.e. 'fake-1.0/some/other_file.txt' was changed to 'fake-1.0/other_file.txt'.But modifications were still required for the manifest. Above change should serve the purpose, I guess. -- hgrepos: +20 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10932 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11862] urlparse.ParseResult to have meaningful __str__
New submission from Tomasz Melcer li...@o2.pl: I find it a minor annoyance that a result of `urlparse.urlparse` (an object of class urlparse.ParseResult) doesn't have a meaningful __str__/__unicode__ methods. `urlparse.ParseResult` is a subclass of `namedtuple` with __slots__, so I can't easily add it, too. I propose to make __str__/__unicode__ equivalent to geturl() call. -- components: Extension Modules messages: 133934 nosy: liori priority: normal severity: normal status: open title: urlparse.ParseResult to have meaningful __str__ type: feature request ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11862 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11783] email parseaddr and formataddr should be IDNA aware
Torsten Becker torsten.bec...@gmail.com added the comment: Hi, here is my revised patch with email.utils.getaddresses() also decoding IDNs. I decided to integrate IDN decoding in AddrlistClass.getaddress() instead of AddrlistClass.getaddrlist() since that function is one level lower and if somebody should ever all it directly, the conversion would not happen. I also fixed a glitch in the docs, versionchanged seems to need two colons to end up in the generated HTML. As a follow up, wouldn't it be helpful if email.Message would do the conversions directly? So when you parse a mail into a Message and access the To field, you get a list of tuples which are decoded properly? For example the following test currently still fails because the quoted header value is not decoded by email.feedparser.FeedParser nor email.Message: def test_email_decodes_idns_and_unicode(self): text = '''\ To: =?utf-8?b?SMOkbnMgV8O8cnN0?= h...@xn--dm-fka.ain Hello World!''' msg = Parser().parsestr(text) self.assertEqual(utils.getaddresses(msg.get_all('To')), [('H\xe4ns W\xfcrst', 'hans@d\xf6m.ain')]) Am I using the package wrong here or is this actually missing? email.header.decode_header seems to be able to do this already but it is not used. Would it be safe to integrate this into the email.message._sanitize_header helper? -- Added file: http://bugs.python.org/file21698/issue-11783-v4.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11783 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11783] email parseaddr and formataddr should be IDNA aware
R. David Murray rdmur...@bitdance.com added the comment: Thanks. I should be able to look at this tomorrow. You are correct about the fact that Message currently doesn't do any decoding. That is part of the design: you get the string out of Message and use the helper decoding functions (decode_header, getaddresses, etc) to get actual usable data out of it. Part of the email6 design addresses this with a new API that will make it much easier to get at the parsed data (methods on a header object returned from msg['xxx']). But for the current package the way it works it the way it is supposed to work ;) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11783 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue984870] curses: getmaxyx() breaks when the window shrinks
akira 4kir4...@gmail.com added the comment: The test produces a traceback while shrinking a window (increasing the window size works ok): Traceback (most recent call last): File screen-resize-bug-curses.py, line 22, in module curses.wrapper(main) File /.../python2.7/curses/wrapper.py, line 43, in wrapper return func(stdscr, *args, **kwds) File screen-resize-bug-curses.py, line 17, in main init_display(stdscr) File screen-resize-bug-curses.py, line 9, in init_display rootwin = stdscr.derwin(20, 50, 0, 0) _curses.error: curses function returned NULL Version info: $ python2.7 -c'import curses; print curses.version' 2.2 -- nosy: +akira ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue984870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11442] list_directory() in SimpleHTTPServer.py should add charset=... to Content-type header
Roundup Robot devnull@devnull added the comment: New changeset bb1695c6cea1 by Martin v. Löwis in branch '2.5': Issue 11442: Add NEWS entry for e9724d7abbc2 http://hg.python.org/cpython/rev/bb1695c6cea1 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11442 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11700] mailbox.py proxy updates
R. David Murray rdmur...@bitdance.com added the comment: Updated patch addressing Stefen and Ezio's comments. -- Added file: http://bugs.python.org/file21699/mailbox_close_twice.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11700 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11849] ElementTree memory leak
Antoine Pitrou pit...@free.fr added the comment: To sum up, python is returning memory, but your libc is not. You can force it using malloc_trim, see the attached patch (I'm not at all suggesting its inclusion, it's just an illustration). That's an interesting thing, perhaps you want to open a feature request as a separate issue? -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11849 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11768] test_signals() of test_threadsignals failure on Mac OS X
STINNER Victor victor.stin...@haypocalc.com added the comment: Oh, I reproduced the bug. [3021] test_threadsignals test_signals (test.test_threadsignals.ThreadSignals) ... test_signals: acquire lock (thread -1610559488) test_signals: wait lock (thread -1610559488) send_signals: enter (thread 27159552) send_signals: raise SIGUSR1 send_signals: raise SIGUSR2 send_signals: release signalled_all send_signals: exit (thread 27159552) ^C There are 2 threads: faulthandler thread and the mainthread. Trace of the main thread: --- (gdb) where #0 0x027a in ___spin_lock () at /System/Library/Frameworks/System.framework/PrivateHeaders/i386/cpu_capabilities.h:216 #1 0x90001433 in pthread_mutex_lock () #2 0x0011b34c in PyThread_acquire_lock_timed (lock=0x1124f10, microseconds=0, intr_flag=0) at Python/thread_pthread.h:450 #3 0x0011b73e in PyThread_acquire_lock (lock=0x1124f10, waitflag=0) at Python/thread_pthread.h:531 #4 0x000775b2 in Py_AddPendingCall (func=0x713dd checksignals_witharg, arg=0x0) at Python/ceval.c:509 #5 0x00071445 in signal_handler (sig_num=31) at ./Modules/signalmodule.c:189 #6 signal handler called #7 0x9010d494 in spin_unlock () #8 0x90001620 in pthread_mutex_lock () #9 0x0011b34c in PyThread_acquire_lock_timed (lock=0x1124f10, microseconds=0, intr_flag=0) at Python/thread_pthread.h:450 #10 0x0011b73e in PyThread_acquire_lock (lock=0x1124f10, waitflag=0) at Python/thread_pthread.h:531 #11 0x000775b2 in Py_AddPendingCall (func=0x713dd checksignals_witharg, arg=0x0) at Python/ceval.c:509 #12 0x00071445 in signal_handler (sig_num=30) at ./Modules/signalmodule.c:189 #13 signal handler called #14 0x900248c7 in semaphore_wait_signal_trap () #15 0x900288b4 in pthread_cond_wait () #16 0x0011b52c in PyThread_acquire_lock_timed (lock=0x1171180, microseconds=-1, intr_flag=1) at Python/thread_pthread.h:476 #17 0x00180746 in acquire_timed (lock=0x1171180, microseconds=-1) at ./Modules/_threadmodule.c:66 #18 0x001809aa in lock_PyThread_acquire_lock (self=0x14ff820, args=0x512038, kwds=0x0) at ./Modules/_threadmodule.c:133 #19 0x0005f58e in PyCFunction_Call (func=0x166c5f8, arg=0x512038, kw=0x0) at Objects/methodobject.c:84 #20 0x0008c1cd in call_function (pp_stack=0xbfff5f64, oparg=0) at Python/ceval.c:3859 #21 0x000869dd in PyEval_EvalFrameEx (f=0x1193798, throwflag=0) at Python/ceval.c:2657 ... --- The main thread was waiting test_signals() lock (signalled_all) while it is was interrupted by a signal. The signal handler calls Py_AddPendingCall() which blocks on acquiring pending_lock. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11768 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11768] test_signals() of test_threadsignals failure on Mac OS X
STINNER Victor victor.stin...@haypocalc.com added the comment: The main thread was waiting test_signals() lock (signalled_all) while it is was interrupted by a signal. The signal handler calls Py_AddPendingCall() which blocks on acquiring pending_lock. Oh, the main thread receives SIGUSR1: the signal handler calls Py_AddPendingCall() to process it later. But while calling Py_AddPendingCall(), it receives a SIGUSR2: the same signal handler is called, and it calls Py_AddPendingCall(). And we have a deadlock because we try to acquire the lock twice, or try to acquire the lock before the lock was released. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11768 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11768] test_signals() of test_threadsignals failure on Mac OS X
Antoine Pitrou pit...@free.fr added the comment: The signal handler calls Py_AddPendingCall() which blocks on acquiring pending_lock. It blocks in taking the mutex, not on waiting for the condition variable. Otherwise it wouldn't block (microseconds = 0). I think the solution is to protect signal_handler() against reentrancy: diff --git a/Modules/signalmodule.c b/Modules/signalmodule.c --- a/Modules/signalmodule.c +++ b/Modules/signalmodule.c @@ -185,10 +185,12 @@ signal_handler(int sig_num) Handlers[sig_num].tripped = 1; /* Set is_tripped after setting .tripped, as it gets cleared in PyErr_CheckSignals() before .tripped. */ -is_tripped = 1; -Py_AddPendingCall(checksignals_witharg, NULL); -if (wakeup_fd != -1) -write(wakeup_fd, \0, 1); +if (!is_tripped) { +is_tripped = 1; +Py_AddPendingCall(checksignals_witharg, NULL); +if (wakeup_fd != -1) +write(wakeup_fd, \0, 1); +} } #ifndef HAVE_SIGACTION -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11768 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11863] Enforce PEP 11 - remove support for legacy systems
New submission from Antoine Pitrou pit...@free.fr: PEP 11 calls for removing support for the following systems in 3.3: Name: Systems using Mach C Threads Unsupported in: Python 3.2 Code removed in: Python 3.3 Name: SunOS lightweight processes (LWP) Unsupported in: Python 3.2 Code removed in: Python 3.3 Name: Systems using --with-pth (GNU pth threads) Unsupported in: Python 3.2 Code removed in: Python 3.3 Name: Systems using Irix threads Unsupported in: Python 3.2 Code removed in: Python 3.3 Name: OSF* systems (issue 8606) Unsupported in: Python 3.2 Code removed in: Python 3.3 -- components: Build, Interpreter Core keywords: easy messages: 133944 nosy: pitrou priority: normal severity: normal stage: needs patch status: open title: Enforce PEP 11 - remove support for legacy systems type: feature request versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11863 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11864] sporadic failure in test_concurrent_futures
New submission from Antoine Pitrou pit...@free.fr: Happened on a buildbot: http://www.python.org/dev/buildbot/all/builders/x86%20Windows7%203.x/builds/2957/steps/test/logs/stdio test test_concurrent_futures failed -- Traceback (most recent call last): File D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\test_concurrent_futures.py, line 276, in test_timeout future1]), finished) AssertionError: Items in the first set but not the second: Future at 0xb802dc8 state=running -- components: Library (Lib), Tests messages: 133945 nosy: bquinlan, pitrou priority: normal severity: normal status: open title: sporadic failure in test_concurrent_futures type: behavior versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11849] ElementTree memory leak
kaifeng cafe...@gmail.com added the comment: I added 'malloc_trim' to the test code and rerun the test with Python 2.5 / 3.2 on CentOS 5.3. The problem still exists. *** Python 2.5.5 final --- PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND 0 2567 pts/0S+ 0:00 0 1 8206 4864 0.4 /home/zkf/.programs/python/bin/python issue11849_test.py 1 2567 pts/0S+ 0:03 0 1 44558 41140 3.9 /home/zkf/.programs/python/bin/python issue11849_test.py 2 2567 pts/0S+ 0:07 0 1 81166 77728 7.5 /home/zkf/.programs/python/bin/python issue11849_test.py 3 2567 pts/0S+ 0:12 0 1 117798 114316 11.0 /home/zkf/.programs/python/bin/python issue11849_test.py 4 2567 pts/0S+ 0:17 0 1 154402 150912 14.5 /home/zkf/.programs/python/bin/python issue11849_test.py 5 2567 pts/0S+ 0:23 0 1 191018 187500 18.1 /home/zkf/.programs/python/bin/python issue11849_test.py 6 2567 pts/0S+ 0:29 0 1 227630 224084 21.6 /home/zkf/.programs/python/bin/python issue11849_test.py 7 2567 pts/0S+ 0:36 0 1 264242 260668 25.1 /home/zkf/.programs/python/bin/python issue11849_test.py 8 2567 pts/0S+ 0:44 0 1 300882 297288 28.7 /home/zkf/.programs/python/bin/python issue11849_test.py 9 2567 pts/0S+ 0:53 0 1 337230 333860 32.2 /home/zkf/.programs/python/bin/python issue11849_test.py END 2567 pts/0S+ 1:02 0 1 373842 370444 35.7 /home/zkf/.programs/python/bin/python issue11849_test.py GC 2567 pts/0S+ 1:02 0 1 373842 370444 35.7 /home/zkf/.programs/python/bin/python issue11849_test.py *** 2567 pts/0S+ 1:02 0 1 373714 370436 35.7 /home/zkf/.programs/python/bin/python issue11849_test.py *** Python 3.2.0 final --- PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND 0 2633 pts/0S+ 0:00 1 1316 11051 6448 0.6 python3.2 issue11849_test.py 1 2633 pts/0S+ 0:02 1 1316 53151 47340 4.5 python3.2 issue11849_test.py 2 2633 pts/0S+ 0:05 1 1316 91051 85216 8.2 python3.2 issue11849_test.py 3 2633 pts/0S+ 0:08 1 1316 128943 124228 12.0 python3.2 issue11849_test.py 4 2633 pts/0S+ 0:11 1 1316 166803 162296 15.6 python3.2 issue11849_test.py 5 2633 pts/0S+ 0:14 1 1316 204475 199972 19.3 python3.2 issue11849_test.py 6 2633 pts/0S+ 0:17 1 1316 243831 238180 23.0 python3.2 issue11849_test.py 7 2633 pts/0S+ 0:20 1 1316 284371 277532 26.8 python3.2 issue11849_test.py 8 2633 pts/0S+ 0:23 1 1316 318187 312456 30.1 python3.2 issue11849_test.py 9 2633 pts/0S+ 0:26 1 1316 360231 353296 34.1 python3.2 issue11849_test.py END 2633 pts/0S+ 0:30 1 1316 393971 388184 37.4 python3.2 issue11849_test.py GC 2633 pts/0S+ 0:30 1 1316 352031 347652 33.5 python3.2 issue11849_test.py *** 2633 pts/0S+ 0:31 1 1316 351903 347524 33.5 python3.2 issue11849_test.py -- versions: +Python 2.7, Python 3.2 Added file: http://bugs.python.org/file21700/issue11849_test2.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11849 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11863] Enforce PEP 11 - remove support for legacy systems
Jesús Cea Avión j...@jcea.es added the comment: I think I toke care of OSF cleanup already. -- nosy: +jcea ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11863 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11241] ctypes: subclassing an already subclassed ArrayType generates AttributeError
Meador Inge mead...@gmail.com added the comment: Verified that this is still broken in the main development branch. The base type should be checked for '_type_' or '_length_' before throwing an error. Attached is a patch that fixes the problem and adds covering tests. The full test suite passed on OS X 10.6.5 and I ran './python.exe -m test -R : -v test_ctype' to verify that I didn't introduce any resource leaks. -- assignee: theller - keywords: +patch nosy: +amaury.forgeotdarc, belopolsky, meador.inge -theller stage: - patch review versions: +Python 2.7, Python 3.1, Python 3.2, Python 3.3 Added file: http://bugs.python.org/file21701/issue-11241.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11241 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10910] pyport.h FreeBSD/Mac OS X fix causes errors in C++ compilation
Meador Inge mead...@gmail.com added the comment: This doesn't look like it has anything to to with the 'ctypes' library component (http://docs.python.org/library/ctypes). So I am removing 'ctypes' from the 'Components' selection. Please correct me if I am wrong ... -- components: -Extension Modules, Library (Lib), Macintosh, Unicode, ctypes nosy: +meador.inge ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10910 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11862] urlparse.ParseResult to have meaningful __str__
Senthil Kumaran sent...@uthcode.com added the comment: What would be a 'meaning' __str__ or __unicode__ of urlparse.urlparse and how would it be useful to you? I would think that people would except a tuple, list or a ParsedResult for such a call. I cannot understand the rational behind the expectation that __str__ or __unicode__ of ParsedResult to be equivalent to the geturl call. If you can, please elaborate. -- assignee: - orsenthil nosy: +orsenthil ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11862 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10910] pyport.h FreeBSD/Mac OS X fix causes errors in C++ compilation
Changes by Meador Inge mead...@gmail.com: -- components: +Macintosh ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10910 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11785] email subpackages documentation problems
ysj.ray ysj@gmail.com added the comment: Oh, sorry, I didn't differ :mod:, :module:, :currentmodule: clearly. But shouldn't the modules link titles in http://docs.python.org/dev/library/email.html display correct module names instead just the email package name? email: Representing character sets seems a little wearied. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11785 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com