[issue9041] raised exception is misleading

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue11860] reference 2.3 has text that runs past the page

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue9896] Introspectable range objects

Daniel Urban 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

[issue11861] 2to3 fails with a ParseError

New submission from Vinay Sajip : 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

[issue11859] test_interrupted_write_text() of test_io failed of Python 3.3 on FreeBSD 7.2

Antoine Pitrou 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 wh

[issue11861] 2to3 fails with a ParseError

Changes by Ezio Melotti : -- nosy: +benjamin.peterson, ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue11276] 2to3: imports fixer doesn't update references to modules specified without attributes

Vinay Sajip 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 __

[issue9762] PEP 3149 related build failures

Jan Groenewald 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

[issue9762] PEP 3149 related build failures

Jan Groenewald added the comment: Oops, correction. Ubuntu 11.04 beta 2 for amd64. -- ___ Python tracker ___ ___ Python-bugs-list mail

[issue10271] warnings.showwarning should allow any callable object

lekma 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://bug

[issue10271] warnings.showwarning should allow any callable object

Changes by lekma : Added file: http://bugs.python.org/file21695/Issue10271.33.test.diff ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue9762] PEP 3149 related build failures

Barry A. Warsaw added the comment: On Apr 17, 2011, at 01:46 PM, Jan Groenewald wrote: >Jan Groenewald 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 inc

[issue11849] ElementTree memory leak

Charles-Francois Natali 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, munma

[issue11849] ElementTree memory leak

Changes by Charles-Francois Natali : -- keywords: +patch Added file: http://bugs.python.org/file21696/gc_trim.diff ___ Python tracker ___

[issue828450] sdist generates bad MANIFEST on Windows

Changes by higery : Removed file: http://bugs.python.org/file21691/change_path_separator_in_MANIFEST.patch ___ Python tracker ___ ___ Python

[issue828450] sdist generates bad MANIFEST on Windows

Changes by higery : Added file: http://bugs.python.org/file21697/change_path_separator_in_MANIFEST.patch ___ Python tracker ___ ___ Python-b

[issue11700] mailbox.py proxy updates

Steffen Daode Nurpmeso 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.

[issue11700] mailbox.py proxy updates

R. David Murray 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 direct

[issue5723] Incomplete json tests

Bob Ippolito 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 -

[issue10932] distutils.core.setup - data_files misbehaviour ?

Prashant Kumar 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).

[issue11862] urlparse.ParseResult to have meaningful __str__

New submission from Tomasz Melcer : 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, t

[issue11783] email parseaddr and formataddr should be IDNA aware

Torsten Becker 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

[issue11783] email parseaddr and formataddr should be IDNA aware

R. David Murray 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, getaddress

[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 curses.wrapper(main) File "/.../python2.7/curses/wrapper.py", l

[issue11442] list_directory() in SimpleHTTPServer.py should add charset=... to Content-type header

Roundup Robot 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

[issue11700] mailbox.py proxy updates

R. David Murray added the comment: Updated patch addressing Stefen and Ezio's comments. -- Added file: http://bugs.python.org/file21699/mailbox_close_twice.patch ___ Python tracker

[issue11849] ElementTree memory leak

Antoine Pitrou 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

[issue11768] test_signals() of test_threadsignals failure on Mac OS X

STINNER Victor 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 271595

[issue11768] test_signals() of test_threadsignals failure on Mac OS X

STINNER Victor 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

[issue11768] test_signals() of test_threadsignals failure on Mac OS X

Antoine Pitrou 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_han

[issue11863] Enforce PEP 11 - remove support for legacy systems

New submission from Antoine Pitrou : 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 i

[issue11864] sporadic failure in test_concurrent_futures

New submission from Antoine Pitrou : 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\

[issue11849] ElementTree memory leak

kaifeng 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 4

[issue11863] Enforce PEP 11 - remove support for legacy systems

Jesús Cea Avión added the comment: I think I toke care of OSF cleanup already. -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-

[issue11241] ctypes: subclassing an already subclassed ArrayType generates AttributeError

Meador Inge 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

[issue10910] pyport.h FreeBSD/Mac OS X "fix" causes errors in C++ compilation

Meador Inge 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, L

[issue11862] urlparse.ParseResult to have meaningful __str__

Senthil Kumaran 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

[issue10910] pyport.h FreeBSD/Mac OS X "fix" causes errors in C++ compilation

Changes by Meador Inge : -- components: +Macintosh ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue11785] email subpackages documentation problems

ysj.ray 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""" s

[issue11241] ctypes: subclassing an already subclassed ArrayType generates AttributeError

Amaury Forgeot d'Arc added the comment: In the patch, _length_ is searched in the class and its base class. But what happens with a third level? class my_array3(my_array2): pass -- ___ Python tracker

[issue11865] typo in Py_AddPendingCall document

New submission from Zhiping Deng : http://docs.python.org/c-api/init.html?highlight=py_addpendingcall#Py_AddPendingCall void Py_AddPendingCall(int (*func)(void *, void *arg)) which should be void Py_AddPendingCall(int (*func)(void *), void *arg) -- assignee: docs@python components: Doc