[issue5650] Obsolete RFCs should be removed from doc of urllib.urlparse
Senthil Kumaran orsent...@gmail.com added the comment: Updated in the r80336 through r80339. Thanks for the note, Ezio. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5650 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6085] Logging in BaseHTTPServer.BaseHTTPRequestHandler causes lag
Charles-Francois Natali neolo...@free.fr 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 rep...@bugs.python.org http://bugs.python.org/issue6085 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8483] asyncore.dispatcher's __getattr__ method produces confusing effects
Dirkjan Ochtman dirk...@ochtman.nl 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 rep...@bugs.python.org http://bugs.python.org/issue8483 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8498] Cannot use backlog = 0 for sockets
New submission from Daniel Evers derm...@googlemail.com: 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 (function socket_listen) the backlog is reset to at least 1. -- components: Extension Modules messages: 103942 nosy: Daniel.Evers severity: normal status: open title: Cannot use backlog = 0 for sockets type: behavior versions: Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8498 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8092] utf8, backslashreplace and surrogates
Changes by STINNER Victor victor.stin...@haypocalc.com: Removed file: http://bugs.python.org/file17010/utf8_surrogate_error-2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8092 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5650] Obsolete RFCs should be removed from doc of urllib.urlparse
Éric Araujo mer...@netwok.org 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 rep...@bugs.python.org http://bugs.python.org/issue5650 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8498] Cannot use backlog = 0 for sockets
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +exarkun ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8498 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug
Changes by STINNER Victor victor.stin...@haypocalc.com: Removed file: http://bugs.python.org/file15863/thread_py_decref.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3299 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug
Changes by STINNER Victor victor.stin...@haypocalc.com: Removed file: http://bugs.python.org/file15880/_curses_panel_py_decref.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3299 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5650] Obsolete RFCs should be removed from doc of urllib.urlparse
Senthil Kumaran orsent...@gmail.com 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. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5650 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8490] asyncore test suite
Antoine Pitrou pit...@free.fr 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 (ZeroDivisionError), if at all possible - in test_set_reuse_addr, if SO_REUSEADDR fails I would suggest skipping the test with self.skip(...), rather than passing silently - in test_set_reuse_addr, sock.close() rather than sock.close - does asyncore support IPv6? test_create_socket checks only AF_INET - do you plan to also test UDP? :) -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8490 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8124] mywrite() ignores PyFile_WriteString() errors
STINNER Victor victor.stin...@haypocalc.com 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 Added file: http://bugs.python.org/file17044/pyfile_writeobject_nosignal.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8124 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5650] Obsolete RFCs should be removed from doc of urllib.urlparse
Éric Araujo mer...@netwok.org 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 rep...@bugs.python.org http://bugs.python.org/issue5650 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8124] mywrite() ignores PyFile_WriteString() errors
STINNER Victor victor.stin...@haypocalc.com 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 calling PyErr_CheckSignals(): * mywrite() should not execute any Python signal handler to avoid raising an * error because mywrite() ignores all errors */ -- Added file: http://bugs.python.org/file17045/mywrite_nosignal.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8124 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8124] mywrite() ignores PyFile_WriteString() errors
Changes by STINNER Victor victor.stin...@haypocalc.com: Removed file: http://bugs.python.org/file17044/pyfile_writeobject_nosignal.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8124 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8124] mywrite() ignores PyFile_WriteString() errors
STINNER Victor victor.stin...@haypocalc.com 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 Python signal handlers. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8124 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5650] Obsolete RFCs should be removed from doc of urllib.urlparse
Senthil Kumaran orsent...@gmail.com 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 bleeding requirement? I doubt. But what is worth is full compliance on all scales with STD 66. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5650 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8195] Crash in sqlite3.create_collation() with a string non encodable to utf8
STINNER Victor victor.stin...@haypocalc.com added the comment: Fixed by r80349 (py3k), r80351 (3.1). -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8195 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8211] configure: ignore AC_PROG_CC hardcoded CFLAGS
STINNER Victor victor.stin...@haypocalc.com 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 rep...@bugs.python.org http://bugs.python.org/issue8211 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8305] memoview[0] creates an invalid view if ndim != 1
Changes by STINNER Victor victor.stin...@haypocalc.com: -- nosy: +benjamin.peterson, georg.brandl, gvanrossum, pitrou, scoder ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8305 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8474] Duplicate tests in email test suite
Ezio Melotti ezio.melo...@gmail.com 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 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8474 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8475] build-installer fix for doc building on OSX 10.4
Martin v. Löwis mar...@v.loewis.de added the comment: Thanks for the patch. Committed as r80355- -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8475 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5650] Obsolete RFCs should be removed from doc of urllib.urlparse
Éric Araujo mer...@netwok.org 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 the disabled tests in test_urlparse). Regards -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5650 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8215] getargs.c in Python3 contains some TODO and the documentation is outdated
Changes by STINNER Victor victor.stin...@haypocalc.com: -- nosy: +barry, benjamin.peterson, brett.cannon, georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8305] memoview[0] creates an invalid view if ndim != 1
Antoine Pitrou pit...@free.fr 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 rep...@bugs.python.org http://bugs.python.org/issue8305 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8498] Cannot use backlog = 0 for sockets
Charles-Francois Natali neolo...@free.fr 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 an implementation-defined minimum value. Furthermore, python's socket documentation makes it clear: Enable a server to accept connections. The backlog argument must be at least 1; it specifies the number of unaccepted connection that the system will allow before refusing new connections. If you really want to only accept 1 connection (I'm talking of sending back a SYN-ACK, not an accept() call), you can just close the server socket as soon as you've done the accept, and re-open it when you're ready to process another request. Or you could accept new connections and close them immediately (but then you'd send back a SYN-ACK then a FIN). So I'd say it's not a python bug. -- assignee: - tarek components: +Distutils -Extension Modules nosy: +neologix, tarek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8498 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8485] Don't accept bytearray as filenames, or simplify the API
STINNER Victor victor.stin...@haypocalc.com 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 related to surrogates in filenames. Fixed: r80361 (py3k), don't backport to 3.1. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8485 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6484] No unit test for mailcap module
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +ezio.melotti priority: low - normal stage: unit test needed - patch review versions: -Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6484 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8496] mailcap.lookup() returns filter iterator rather than list if key is given
Antoine Pitrou pit...@free.fr added the comment: Looks goot to me. -- nosy: +pitrou priority: - normal stage: - patch review versions: +Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8496 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8496] mailcap.lookup() returns filter iterator rather than list if key is given
Antoine Pitrou pit...@free.fr added the comment: Good, sorry. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8496 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6484] No unit test for mailcap module
Changes by STINNER Victor victor.stin...@haypocalc.com: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6484 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8498] Cannot use backlog = 0 for sockets
Jean-Paul Calderone exar...@twistedmatrix.com 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 argument. And 0 seems to have a very different meaning than 1, but for some reason CPython thinks that 1 is a better thing for 0 to mean. Perhaps there is a real reason someone thought to add this check in sock_listen, but if not, I think it's worth considering removing this check. Unfortunately the commit message for the revision which added this check (r3880) is not informative: sock_listen: ensure backlog argument is at least1 If you really want to only accept 1 connection (I'm talking of sending back a SYN-ACK, not an accept() call), you can just close the server socket This makes perfect sense, though, and is good advice in general. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8498 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7332] python script segment fault at PyMarshal_ReadLastObjectFromFile in import_submodule
resc thomat...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue7332 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8475] build-installer fix for doc building on OSX 10.4
Martin v. Löwis mar...@v.loewis.de added the comment: It seems to work fine, so merged as r80365, r80366, r80367. -- resolution: - accepted status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8475 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8482] test_gdb - (unable to read python frame information) mismatch
Dave Malcolm dmalc...@redhat.com 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 various locations within the
implementation of PyEval_EvalFrameEx.
The DWARF debug data contains a mapping between ranges of program counter
values and methods for calculating the values of variables, and in many
locations within PyEval_EvalFrameEx, it doesn't have enough information to
figure out what the value of f is.
It works on i386: the calling conventions are different, and it's fairly easy
for gdb to walk up the stack and find f.
I believe my RH colleagues who hack on gcc and gdb are working on improving
this so that DWARF can handle such cases (where f doesn't change during the
function call), but Jakub describes that as at least a year from now
In the meantime there are some options.
(i) A dirty hack is that in some places in the function on x86_64 I've seen
that the value of f is stored in the $rbp register. We could use something
like this as a fallback for when directly querying gdb for f fails:
_type_PyFrameObjectPtr = gdb.lookup_type('PyFrameObject').pointer()
f = gdb.parse_and_eval('$rbp').cast(_type_PyFrameObjectPtr)
and then see if the value looks sane (e.g. does it have a meaningful ob_type?
does 0 ==strcmp($rbp-ob_type-tp_name, frame); if so, then that's probably
the value of f, and use it.
Obviously that would be highly fragile; it may be something I'm seeing on my
particular version of gcc, but might not work for other people's gcc. Also I
suspect that it will give misleading results when traversing the stack of
C-level frames.
Another approach would be to simply accept that it isn't going to work on
x86_64 with gcc with optimizations turned on until a later version of gcc.
We could handle this:
(ii) by trying to detect this situation during test_gdb.py, and to skip the
affected tests.
(iii) by generalizing the tests so that they can handle the case where
arbitrary frames aren't readable.
Approach (iii) seems most promising to me, and I'll try to cook up a patch
(though I want to try approach (i), as it would be nice to get visibility into
these frames)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8482
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7332] python script segment fault at PyMarshal_ReadLastObjectFromFile in import_submodule
resc thomat...@gmail.com 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. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7332 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8498] Cannot use backlog = 0 for sockets
Changes by Tarek Ziadé ziade.ta...@gmail.com: -- assignee: tarek - components: +Library (Lib) -Distutils ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8498 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8494] test_gdb assertEndsWith failing: Unable to read information on python frame
Dave Malcolm dmalc...@redhat.com 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 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8494 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8496] mailcap.lookup() returns filter iterator rather than list if key is given
Antoine Pitrou pit...@free.fr added the comment: Committed in r80369. Thanks! -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8496 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8482] test_gdb - (unable to read python frame information) mismatch
Nick Coghlan ncogh...@gmail.com 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 quick and dirty approach would be a variant of ii. that just skipped the offending test for GCC on x86_64 machines. The platform library would make that fairly straightforward: platform.python_compiler() 'GCC 4.4.1' platform.machine() 'x86_64' -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8482 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8482] test_gdb, gdb/libpython.py: Unable to read information on python frame
STINNER Victor victor.stin...@haypocalc.com 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 information on python frame) on my i386 computer (32 bits) with -O1 (but it doesn't with -O0). I'm using Debian Sid: gcc 4.4.3 and gdb 7.1. -- title: test_gdb - (unable to read python frame information) mismatch - test_gdb, gdb/libpython.py: Unable to read information on python frame ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8482 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7865] io close() swallowing exceptions
Pascal Chambon chambon.pas...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue7865 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7865] io close() swallowing exceptions
Changes by STINNER Victor victor.stin...@haypocalc.com: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7865 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8499] Set a timeout in test_urllibnet
New submission from STINNER Victor victor.stin...@haypocalc.com: 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_urllibnet failed -- multiple errors occurred; run in verbose mode for details --- (the test was executed again, but www.python.org was back) test_urllib should use a timeout, as done for test_urllib2: see #8460. -- components: Library (Lib), Tests messages: 103971 nosy: haypo, orsenthil severity: normal status: open title: Set a timeout in test_urllibnet versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8499 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8490] asyncore test suite
Giampaolo Rodola' g.rod...@gmail.com 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 use_poll in loop_waiting_for_flag() whoops! thanks - calling time.sleep() in loop_waiting_for_flag() looks wrong to me time.sleep() in that loop grants that the condition is retried for at least 1 second before failing the test. By removing time.sleep() a test which is supposed to fail will fail almost immediately. - test_handle_error should check that the exception state is the expected one (ZeroDivisionError), if at all possible Good advice, done. - in test_set_reuse_addr, if SO_REUSEADDR fails I would suggest skipping the test with self.skip(...), done in test_set_reuse_addr, sock.close() rather than sock.close whoops =) does asyncore support IPv6? test_create_socket checks only AF_INET I don't think it would worth it. create_socket() is just a thin wrapper around socket.socket(). Actually I wasn't even sure to add that test or not. - do you plan to also test UDP? :) Unfortunately asyncore does not support UDP. At a first look it would seems so, since create_socket() accepts two parameters, family and *type*: def create_socket(self, family, type): sock = socket.socket(family, type) ...but actually we can only use SOCK_STREAM, as the API just takes care of wrapping send() and recv() calls, not recvfrom() and sendto(). -- Added file: http://bugs.python.org/file17047/asyncore.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8490 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8500] Erroneous Invalid Syntax Error
New submission from Zach Lym zach...@indolering.com: I love you python File stdin, 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 Syntax Error type: compile error versions: Python 2.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8500 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8493] socket's send can raise errno 35 under OS X, which causes problems in sendall
Charles-Francois Natali neolo...@free.fr 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 improve things, you should probably wait a little before retrying. Furthermore, if you get this type of error, it's probably because you're using non-blocking sockets. And if it's the case, you should be prepared to this type of transient error, and use socket.send instead (so that you can sleep, retry, etc if necesssary). -- nosy: +exarkun, neologix ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8493 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8500] Erroneous Invalid Syntax Error
Ezio Melotti ezio.melo...@gmail.com added the comment: Except the report :) -- nosy: +ezio.melotti resolution: - invalid stage: - committed/rejected status: open - closed type: compile error - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8500 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8500] Erroneous Invalid Syntax Error
Antoine Pitrou pit...@free.fr added the comment: Surely you forgot to capitalize Python, not to mention the lack of punctuation. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8500 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6085] Logging in BaseHTTPServer.BaseHTTPRequestHandler causes lag
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +orsenthil priority: - normal versions: +Python 3.2 -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6085 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8092] utf8, backslashreplace and surrogates
STINNER Victor victor.stin...@haypocalc.com added the comment: Fixed: r80382 (py3k), r80383 (3.1). -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8092 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8498] Cannot use backlog = 0 for sockets
Daniel Evers derm...@googlemail.com 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 situation: 1. Always set backlog at least to 1 (like now), but make this explicit in the documentation (docs.python.org says should be at least 1 which is not the same as will be at least 1) 2. Allow backlog = 0 and make a note in the docs that the exact behaviour will be implementation/OS-specific. In case (1) the hint to close the listen socket should also be added to the documentation. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8498 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8501] --dry-run option doesn't work
New submission from Jim Fulton j...@zope.com: 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://docs.python.org/distutils/introduction.html#a-simple-example and then try the option. See also: http://mail.python.org/pipermail/distutils-sig/2010-April/016000.html -- assignee: tarek components: Distutils messages: 103979 nosy: j1m, tarek severity: normal status: open title: --dry-run option doesn't work type: behavior versions: Python 2.5, Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8501 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8501] --dry-run option doesn't work
Changes by Tarek Ziadé ziade.ta...@gmail.com: -- priority: - normal resolution: - accepted versions: +Python 2.7, Python 3.1, Python 3.2, Python 3.3 -Python 2.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8501 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7384] curses crash on FreeBSD
Roumen Petrov bugtr...@roumenpetrov.info 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 rep...@bugs.python.org http://bugs.python.org/issue7384 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8211] configure: ignore AC_PROG_CC hardcoded CFLAGS
Ned Deily n...@acm.org added the comment: I think the issue can be closed again. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8211 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8484] ssl socket with certificate verification fails on SHA256 digest algorithm
Roumen Petrov bugtr...@roumenpetrov.info added the comment: Probably test case will fail is sha256 module is not loaded - openssl versions before 0.9.8 -- nosy: +rpetrov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8484 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8211] configure: ignore AC_PROG_CC hardcoded CFLAGS
STINNER Victor victor.stin...@haypocalc.com 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 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8211 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8484] ssl socket with certificate verification fails on SHA256 digest algorithm
Antoine Pitrou pit...@free.fr 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 rep...@bugs.python.org http://bugs.python.org/issue8484 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4768] email.generator.Generator object bytes/str crash - b64encode() bug?
Changes by Éric Araujo mer...@netwok.org: -- nosy: +merwok ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4768 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4768] email.generator.Generator object bytes/str crash - b64encode() bug?
Changes by Antoine Pitrou pit...@free.fr: -- priority: - high stage: - patch review versions: +Python 3.1, Python 3.2 -Python 3.0 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4768 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8465] re: Backreferences vs. escapes: a silent failure solved
Antoine Pitrou pit...@free.fr added the comment: Not sure why this was assigned to me. -- assignee: pitrou - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8465 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8465] re: Backreferences vs. escapes: a silent failure solved
Changes by Antoine Pitrou pit...@free.fr: -- nosy: -pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8465 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8498] Cannot use backlog = 0 for sockets
Antoine Pitrou pit...@free.fr 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 rep...@bugs.python.org http://bugs.python.org/issue8498 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8498] Cannot use backlog = 0 for sockets
Changes by Antoine Pitrou pit...@free.fr: -- priority: - low versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8498 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8108] test_ftplib fails with OpenSSL 0.9.8m
Antoine Pitrou pit...@free.fr 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: - fixed stage: patch review - committed/rejected status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8108 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8502] proposal: encourage xgettext rather than pygettext.py in gettext docs
New submission from jhg j...@upb.de: 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 cannot cope with plurals, i.e. ngettext(). xgettext can do that just fine. Since pygettext.py was not modified in 5 years I propose changing the documentation of gettext to encourage xgettext rather than pygettext.py. My proposed changes are attached (edited as text file; I do not know how to convert it to a webpage and hence did not test that). I used the 2.7b1 documentation, but the patch appears to apply just as well to the 3.1.2 documentation. -- assignee: georg.brandl components: Documentation files: gettext.txt.patch keywords: patch messages: 103988 nosy: georg.brandl, jhg severity: normal status: open title: proposal: encourage xgettext rather than pygettext.py in gettext docs versions: Python 2.7 Added file: http://bugs.python.org/file17048/gettext.txt.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8502 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4768] email.generator.Generator object bytes/str crash - b64encode() bug?
Changes by R. David Murray rdmur...@bitdance.com: -- assignee: barry - r.david.murray resolution: - accepted type: crash - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4768 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
