[issue4768] email.generator.Generator object bytes/str crash - b64encode() bug?

Changes by R. David Murray : -- assignee: barry -> r.david.murray resolution: -> accepted type: crash -> behavior ___ Python tracker ___ _

[issue8502] proposal: encourage xgettext rather than pygettext.py in gettext docs

New submission from jhg : Wanting to figure out how to support multiple languages in my applications I read the gettext documentation and got to the part saying one should use pygettext.py to create .po files. After copying that program from the python SVN repository I later found out that it

[issue8108] test_ftplib fails with OpenSSL 0.9.8m

Antoine Pitrou added the comment: Patch committed to r80392 (trunk) and r80394 (py3k). Am pondering a partial backport of the SSL shutdown fixes to 2.6 and 3.1 (test_ftplib doesn't need any backport since it doesn't support TLS in these branches). -- assignee: -> pitrou resolution:

[issue8498] Cannot use backlog = 0 for sockets

Changes by Antoine Pitrou : -- priority: -> low versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___ ___ Python-bugs-l

[issue8498] Cannot use backlog = 0 for sockets

Antoine Pitrou added the comment: The request to allow 0 looks reasonable to me. Now if someone wants to propose a patch (+ tests if there's any way of testing for this). -- nosy: +pitrou ___ Python tracker __

[issue8465] re: Backreferences vs. escapes: a silent failure solved

Changes by Antoine Pitrou : -- nosy: -pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue8465] re: Backreferences vs. escapes: a silent failure solved

Antoine Pitrou added the comment: Not sure why this was assigned to me. -- assignee: pitrou -> ___ Python tracker ___ ___ Python-bugs

[issue4768] email.generator.Generator object bytes/str crash - b64encode() bug?

Changes by Antoine Pitrou : -- priority: -> high stage: -> patch review versions: +Python 3.1, Python 3.2 -Python 3.0 ___ Python tracker ___

[issue4768] email.generator.Generator object bytes/str crash - b64encode() bug?

Changes by Éric Araujo : -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue8484] ssl socket with certificate verification fails on SHA256 digest algorithm

Antoine Pitrou added the comment: > Probably test case will fail is sha256 module is not loaded - openssl > versions before 0.9.8 Yes, this has been fixed in r80375. -- ___ Python tracker

[issue8211] configure: ignore AC_PROG_CC hardcoded CFLAGS

STINNER Victor added the comment: Even if this issue doesn't fix all the configure "complete mess", I think that it improves it a little bit. Open new issues if you would like to fix other parts of the configure script. -- resolution: -> fixed status: open -> closed

[issue8484] ssl socket with certificate verification fails on SHA256 digest algorithm

Roumen Petrov added the comment: Probably test case will fail is sha256 module is not loaded - openssl versions before 0.9.8 -- nosy: +rpetrov ___ Python tracker ___ ___

[issue8211] configure: ignore AC_PROG_CC hardcoded CFLAGS

Ned Deily added the comment: I think the issue can be closed again. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue7384] curses crash on FreeBSD

Roumen Petrov added the comment: Instead to test in setup.py we could use result from configure script - just uncomment line and use it -- nosy: +rpetrov ___ Python tracker ___

[issue8501] --dry-run option doesn't work

Changes by Tarek Ziadé : -- priority: -> normal resolution: -> accepted versions: +Python 2.7, Python 3.1, Python 3.2, Python 3.3 -Python 2.5 ___ Python tracker ___

[issue8501] --dry-run option doesn't work

New submission from Jim Fulton : The --dry-run option is ignored by the install command. It leads to an error when used as a global option. It should be fixed or removed. I vote for removal, but don't really care. Removal seems easier. :) To reproduce, create the simple project: http://doc

[issue8498] Cannot use backlog = 0 for sockets

Daniel Evers added the comment: Thanks for your help. I'll close the listen socket. Nevertheless I'd like to understand the check in sock_listen. The commit message is not very helpful, I agree, that's why I wrote this issue. 0 is a valid value, and I'd suggest two ways to handle this situati

[issue8092] utf8, backslashreplace and surrogates

STINNER Victor added the comment: Fixed: r80382 (py3k), r80383 (3.1). -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue6085] Logging in BaseHTTPServer.BaseHTTPRequestHandler causes lag

Changes by Antoine Pitrou : -- nosy: +orsenthil priority: -> normal versions: +Python 3.2 -Python 2.6 ___ Python tracker ___ ___ Pytho

[issue8500] Erroneous Invalid Syntax Error

Antoine Pitrou added the comment: Surely you forgot to capitalize Python, not to mention the lack of punctuation. -- nosy: +pitrou ___ Python tracker ___

[issue8500] Erroneous Invalid Syntax Error

Ezio Melotti added the comment: Except the report :) -- nosy: +ezio.melotti resolution: -> invalid stage: -> committed/rejected status: open -> closed type: compile error -> behavior ___ Python tracker __

[issue8493] socket's send can raise errno 35 under OS X, which causes problems in sendall

Charles-Francois Natali added the comment: The problem is that if you run out of "network buffers" (I guess it's equivalent to Unix socket buffers), what do you do ? If the network or the receiving host is congested, spinning around the send call trying to resend the data isn't going to improv

[issue8500] Erroneous Invalid Syntax Error

New submission from Zach Lym : >>> I love you python File "", line 1 I love you python ^ SyntaxError: invalid syntax >>> There is nothing invalid about that! -- components: None messages: 103973 nosy: indolering severity: normal status: open title: Erroneous Invalid Synta

[issue8490] asyncore test suite

Giampaolo Rodola' added the comment: > should be 'listens' [...] > should be 'bound' done > I'd prefer to see a 'BaseTestAPI' that has no base class, and two > TestCase subclasses that use BaseTestAPI as a mixin, one for > use_poll=True and one for use_poll=False. done > - you don't use us

[issue8499] Set a timeout in test_urllibnet

New submission from STINNER Victor : As #8460 (test_urllib2net), test_urllibnet fails if a website doesn't answer. Today, it was www.python.org during few minutes: http://www.python.org/dev/buildbot/all/builders/amd64 gentoo 3.1/builds/482/steps/test/logs/stdio --- test_urllibnet test test_url

[issue7865] io close() swallowing exceptions

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue7865] io close() swallowing exceptions

Pascal Chambon added the comment: Patch and test to stop swallowing exceptions on stream close(), for python SVN trunk. -- keywords: +patch Added file: http://bugs.python.org/file17046/release_io_close_exceptions.patch ___ Python tracker

[issue8482] test_gdb, gdb/libpython.py: Unable to read information on python frame

STINNER Victor added the comment: > the issue is that on 64-bit gcc builds with enough optimization, > the argument "PyFrameObject *f" is passed as a register, > and that gets clobbered at various locations within the > implementation of PyEval_EvalFrameEx. test_gdb fails (Unable to read info

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Nick Coghlan added the comment: Thanks, I understood your summary significantly better than I did the bug discussion :) Any of your 3 options sounds reasonable to me (although i. sounds potentially fragile in the face of different versions of gcc, so iii. might be necessary anyway). The qui

[issue8496] mailcap.lookup() returns filter iterator rather than list if key is given

Antoine Pitrou added the comment: Committed in r80369. Thanks! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue8494] test_gdb assertEndsWith failing: Unable to read information on python frame

Dave Malcolm added the comment: Thanks - yes, this does indeed look like a dup of issue 8482; resolving it as such. -- resolution: -> duplicate status: open -> closed superseder: -> test_gdb - "(unable to read python frame information)" mismatch _

[issue8498] Cannot use backlog = 0 for sockets

Changes by Tarek Ziadé : -- assignee: tarek -> components: +Library (Lib) -Distutils ___ Python tracker ___ ___ Python-bugs-list maili

[issue7332] python script segment fault at PyMarshal_ReadLastObjectFromFile in import_submodule

resc added the comment: Argh, that e-mail didn't work. Anyway, I just wanted to say that the kernel explanation is consistent with my experience, I had a crash every week up until recently, when I upgraded, but in the past few days I haven't been able to reproduce it. -- __

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Dave Malcolm added the comment: See https://bugzilla.redhat.com/show_bug.cgi?id=556975#c21 I'll try to summarize: as I understand things, the issue is that on 64-bit gcc builds with enough optimization, the argument "PyFrameObject *f" is passed as a register, and that gets clobbered at variou

[issue8475] build-installer fix for doc building on OSX 10.4

Martin v. Löwis added the comment: It seems to work fine, so merged as r80365, r80366, r80367. -- resolution: -> accepted status: open -> closed ___ Python tracker ___ _

[issue7332] python script segment fault at PyMarshal_ReadLastObjectFromFile in import_submodule

resc added the comment: > This was fixed in stable releases of the Ubuntu > kernels on Mar 16, 2010 (though the fix was > included in Ubuntu 9.10 when it was released > Oct 29, 2009). -- ___ Python tracker

[issue8498] Cannot use backlog = 0 for sockets

Jean-Paul Calderone added the comment: > Furthermore, python's socket documentation makes it clear: Why does CPython go out of its way to make it impossible to pass 0 to the platform listen() API? The part of the specification you quoted makes it very clear that 0 is a valid value for this a

[issue6484] No unit test for mailcap module

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue8496] mailcap.lookup() returns filter iterator rather than list if key is given

Antoine Pitrou added the comment: Good, sorry. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue8496] mailcap.lookup() returns filter iterator rather than list if key is given

Antoine Pitrou added the comment: Looks goot to me. -- nosy: +pitrou priority: -> normal stage: -> patch review versions: +Python 3.1 ___ Python tracker ___ ___

[issue6484] No unit test for mailcap module

Changes by Antoine Pitrou : -- nosy: +ezio.melotti priority: low -> normal stage: unit test needed -> patch review versions: -Python 2.7 ___ Python tracker ___ __

[issue8485] Don't accept bytearray as filenames, or simplify the API

STINNER Victor added the comment: MvL, MaL and Antoine Pitrou agreed to drop support of bytearray filenames in Python. I choosed to remove it directly in Python 3.2 because it wasn't really used, open() and os.path never supported bytearray filenames, and I will simplify the other issues rela

[issue8498] Cannot use backlog = 0 for sockets

Charles-Francois Natali added the comment: That's a non-portable user of listen()'s backlog, see http://www.opengroup.org/onlinepubs/009695399/functions/listen.html: A backlog argument of 0 may allow the socket to accept connections, in which case the length of the listen queue may be set to a

[issue8305] memoview[0] creates an invalid view if ndim != 1

Antoine Pitrou added the comment: I'll leave this to our numpy experts. I don't even know how to unit test this without installing numpy. -- assignee: -> teoliphant priority: -> normal stage: -> needs patch ___ Python tracker

[issue8215] getargs.c in Python3 contains some TODO and the documentation is outdated

Changes by STINNER Victor : -- nosy: +barry, benjamin.peterson, brett.cannon, georg.brandl ___ Python tracker ___ ___ Python-bugs-list

[issue5650] Obsolete RFCs should be removed from doc of urllib.urlparse

Éric Araujo added the comment: (Not sure I understand “bleeding requirement”, but I get the gist.) Full compliance with STD 66 is indeed the most desirable goal, thanks for your work in that direction! I just thought that some corner cases were not compliant because of backwards compat (hence t

[issue8475] build-installer fix for doc building on OSX 10.4

Martin v. Löwis added the comment: Thanks for the patch. Committed as r80355- -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-

[issue8474] Duplicate tests in email test suite

Ezio Melotti added the comment: Fixed in r80350 (trunk), r80352 (release26-maint), r80353 (py3k) and r80354 (release31-maint), thanks for the patch! -- nosy: +ezio.melotti priority: -> normal resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: +Python

[issue8305] memoview[0] creates an invalid view if ndim != 1

Changes by STINNER Victor : -- nosy: +benjamin.peterson, georg.brandl, gvanrossum, pitrou, scoder ___ Python tracker ___ ___ Python-bug

[issue8211] configure: ignore AC_PROG_CC hardcoded CFLAGS

STINNER Victor added the comment: Issue #8366 was caused by a fix of issue #1628484 (and ok, indirectly by my change). Issue #8366 is now fixed. Can I close this issue again or do you think that there is still something to do? -- ___ Python tracker

[issue8195] Crash in sqlite3.create_collation() with a string non encodable to utf8

STINNER Victor added the comment: Fixed by r80349 (py3k), r80351 (3.1). -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue5650] Obsolete RFCs should be removed from doc of urllib.urlparse

Senthil Kumaran added the comment: On Thu, Apr 22, 2010 at 11:08:01AM +, Éric Araujo wrote: > Thanks for the explanation. Would it make sense to have either different > functions or a switch to existing ones to tell if we want legacy or > modern parsing? Hard at the moment, or is it a bleed

[issue8124] mywrite() ignores PyFile_WriteString() errors

STINNER Victor added the comment: The goal is this issue is also to catch SIGINT when starting Python. It now works in Python trunk and py3k, but not in verbose mode because mywrite() eats errors (especially the KeyboardInterrupt raised by the default SIGINT handler) and calls indirectly Pyth

[issue8124] mywrite() ignores PyFile_WriteString() errors

Changes by STINNER Victor : Removed file: http://bugs.python.org/file17044/pyfile_writeobject_nosignal.patch ___ Python tracker ___ ___ Python-

[issue8124] mywrite() ignores PyFile_WriteString() errors

STINNER Victor added the comment: Ok, forget my pyfile_writeobject_nosignal.patch, it's not the right approach. New patch: mywrite() uses its own implementation PyFile_WriteString(), sys_pyfile_write(), which doesn't call PyErr_CheckSignals(): /* Implementation of PyFile_WriteString() no cal

[issue5650] Obsolete RFCs should be removed from doc of urllib.urlparse

Éric Araujo added the comment: Thanks for the explanation. Would it make sense to have either different functions or a switch to existing ones to tell if we want legacy or modern parsing? -- ___ Python tracker

[issue8124] mywrite() ignores PyFile_WriteString() errors

STINNER Victor added the comment: Attached patch fixes this issue: PyFile_WriteObject() doesn't call PyObject_Str() to avoid PyErr_CheckSignals(). I'm not sure that it's the right approch because it may change the behaviour of existing code when getting a signal. -- keywords: +patch

[issue8490] asyncore test suite

Antoine Pitrou added the comment: Some remarks: - I agree with RDM's comment regarding inheritance - you don't use use_poll in loop_waiting_for_flag() - calling time.sleep() in loop_waiting_for_flag() looks wrong to me - test_handle_error should check that the exception state is the expected one

[issue5650] Obsolete RFCs should be removed from doc of urllib.urlparse

Senthil Kumaran added the comment: It was intentional as not to remove the old RFC references because certain parsing behaviours follow them compatibility purposes. If you look at test_urlparse.py you might get the specifics of parsing corresponding a RFC. -- __

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Changes by STINNER Victor : Removed file: http://bugs.python.org/file15880/_curses_panel_py_decref.patch ___ Python tracker ___ ___ Python-bugs

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Changes by STINNER Victor : Removed file: http://bugs.python.org/file15863/thread_py_decref.patch ___ Python tracker ___ ___ Python-bugs-list m

[issue8498] Cannot use backlog = 0 for sockets

Changes by Antoine Pitrou : -- nosy: +exarkun ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue5650] Obsolete RFCs should be removed from doc of urllib.urlparse

Éric Araujo added the comment: Hello You’ve added references to current RFCs without removing obsolete ones. Why not remove mention of obsoleted RFCs? Regards -- ___ Python tracker __

[issue8092] utf8, backslashreplace and surrogates

Changes by STINNER Victor : Removed file: http://bugs.python.org/file17010/utf8_surrogate_error-2.patch ___ Python tracker ___ ___ Python-bugs-

[issue8498] Cannot use backlog = 0 for sockets

New submission from Daniel Evers : I'm trying to rewrite a server application in python that accepts exactly 1 connection. I have a previous version written in C that can call listen() on a socket with a backlog of 0 connections, but this is not possible in python. In Modules/socketmodule.c (f

[issue8483] asyncore.dispatcher's __getattr__ method produces confusing effects

Dirkjan Ochtman added the comment: I definitely like the patch, but ideally we would also have a patch adding a __str__ on dispatcher, right? Which would just return the repr(self) result. -- ___ Python tracker __

[issue6085] Logging in BaseHTTPServer.BaseHTTPRequestHandler causes lag

Charles-Francois Natali added the comment: Yes, performing a DNS resolution every time we log something is definitely sub-optimal. We should perform it only once, and cache the result. -- nosy: +neologix ___ Python tracker