[issue8858] socket.getaddrinfo returns wrong results for IPv6 addresses

Martin v. Löwis added the comment: What operating system is this on? What exact Python version are you using? I can't reproduce this with r81614 on Linux. -- nosy: +loewis ___ Python tracker __

[issue8859] split() splits on non whitespace char when ther is no separator given.

Raymond Hettinger added the comment: I also agree this should be closed. -- nosy: +rhettinger status: open -> closed ___ Python tracker ___ __

[issue8787] warnings inside PyRun_SimpleString() display argv[1]

Benjamin Peterson added the comment: First of all, your patch needs a test. -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Pyt

[issue8787] warnings inside PyRun_SimpleString() display argv[1]

Sebastian added the comment: any news on this? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue7946] Convoy effect with I/O bound threads and New GIL

Gregory P. Smith added the comment: Thanks for all your work Nir! I personally think the BFS approach is the best we've seen yet for this problem! Having read the thread you linked to in full (ignoring the tagents bikeshedding and mudslinging that went on there), it sounds like the general

[issue6560] socket sendmsg(), recvmsg() methods

Changes by Andrew Grover : -- nosy: +Andrew.Grover ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue7983] The encoding map from Unicode to CP932 is different from that of Windows'

Marc-Andre Lemburg added the comment: Hye-Shik, could you please comment on this ? The Windows version appears to replace private use code points with CJK compatibility idiographs, ie. uses standard Unicode code points rather than private escape code points (for round-trip safety). -

[issue7946] Convoy effect with I/O bound threads and New GIL

Nir Aides added the comment: Updated bfs.patch with BSD license and copyright notice. ! Current version patches cleanly and builds with Python revision svn r81201. Issue 7946 and proposed patches were put on hold indefinitely following this python-dev discussion: http://mail.python.org/piper

[issue7946] Convoy effect with I/O bound threads and New GIL

Changes by Nir Aides : Removed file: http://bugs.python.org/file17356/bfs.patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue8859] split() splits on non whitespace char when ther is no separator given.

Ezio Melotti added the comment: I think the problem is in the default encoding used when you call unicode() without specifying any encoding. >>> '\xc5\xa0'.decode('iso-8859-1').split() [u'\xc5'] >>> '\xc5\xa0'.decode('utf-8').split() [u'\u0160'] --

[issue8859] split() splits on non whitespace char when ther is no separator given.

Peter Landgren added the comment: I am not sure I can follow you. I will try to be more specific. The test string consists originally of one character; the Czech Š. 1. On Linux with Python 2.6.4 1.1 If I keep the original code line order: label = obj.get() print type(label), repr(label) label

[issue8807] poplib should support SSL contexts

Antoine Pitrou added the comment: There's the problem mentioned by Ezio: it breaks compatibility if someone passed a timeout to POP3_SSL by position (rather than by name). -- ___ Python tracker ___

[issue8859] split() splits on non whitespace char when ther is no separator given.

Antoine Pitrou added the comment: Oh, and I agree with Ezio, this is most likely not a bug at all and should probably be closed. -- ___ Python tracker ___ __

[issue8859] split() splits on non whitespace char when ther is no separator given.

Antoine Pitrou added the comment: What do you mean, "works perfectly well under Linux"? The error also happens under Linux here, and is expected: you can't call unicode() without an encoding and expect it to decode properly non-ASCII chars (and \xa0 is a non-ASCII char). -- nosy: +pit

[issue8859] split() splits on non whitespace char when ther is no separator given.

Ezio Melotti added the comment: Both on Linux and Windows I get: >>> '\xa0'.isspace() False >>> u'\xa0'.isspace() True The Unicode char u'\xa0' is U+00A0 NO-BREAK SPACE, so unicode.split correctly considers it a whitespace. However '\xa0' is not a whitespace, so str.split ignores it. The corre

[issue8859] split() splits on non whitespace char when ther is no separator given.

New submission from Peter Landgren : When the variable label is equal to '\xc5\xa0 Z\nX W' this line sequence label = " ".join(label.split()) label = unicode(label) results in: 7347: ERROR: gramps.py: line 138: Unhandled exception Traceback (most recent call last): File "C:\Program Files (x86)\

[issue8748] integer-to-complex comparisons give incorrect results

Meador Inge added the comment: [Mark] > Can you think of any reason that we shouldn't just copy the py3k > implementation ... Not that I can think of. Like you pointed out, we should have removed the coercion from the rich comparison when fixing issue 5211. > Thanks for all your help with

[issue8857] socket.getaddrinfo needs tests

Changes by Antoine Pitrou : Added file: http://bugs.python.org/file17503/doc-getaddrinfo.patch ___ Python tracker ___ ___ Python-bugs-list mail

[issue8857] socket.getaddrinfo needs tests

Changes by Antoine Pitrou : Removed file: http://bugs.python.org/file17502/doc-getaddrinfo.patch ___ Python tracker ___ ___ Python-bugs-list ma

[issue8857] socket.getaddrinfo needs tests

Antoine Pitrou added the comment: Here is a possible doc patch for getaddrinfo(). Comments? -- keywords: +patch Added file: http://bugs.python.org/file17502/doc-getaddrinfo.patch ___ Python tracker

[issue8857] socket.getaddrinfo needs tests

Antoine Pitrou added the comment: It also needs better documentation, by the way. -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue8853] getaddrinfo should accept port of type long

Antoine Pitrou added the comment: See issue8857 for the tests issue. -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mail

[issue8858] socket.getaddrinfo returns wrong results for IPv6 addresses

Changes by Antoine Pitrou : -- nosy: +exarkun, giampaolo.rodola, mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue8858] socket.getaddrinfo returns wrong results for IPv6 addresses

New submission from Antoine Pitrou : It seems socket.getaddrinfo gives wrong results for IPv6 address under py3k: >>> pprint.pprint(socket.getaddrinfo("www.python.org", 0)) [(2, 1, 6, '', ('82.94.164.162', 0)), (2, 2, 17, '', ('82.94.164.162', 0)), (2, 3, 0, '', ('82.94.164.162', 0)), (10, 1,

[issue8857] socket.getaddrinfo needs tests

Changes by Antoine Pitrou : -- nosy: +exarkun, giampaolo.rodola, mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue8857] socket.getaddrinfo needs tests

New submission from Antoine Pitrou : socket.getaddrinfo has no tests at all. This should be fixed. -- components: Library (Lib), Tests messages: 106767 nosy: pitrou priority: high severity: normal status: open title: socket.getaddrinfo needs tests type: behavior versions: Python 2.6, Pyt

[issue8853] getaddrinfo should accept port of type long

Mark Dickinson added the comment: The attached patch should fix the problem. I'm not sure how to test it, though: the socket module currently seems to have exactly 0 tests for socket.getaddrinfo. -- keywords: +patch nosy: +mark.dickinson Added file: http://bugs.python.org/file17501/

[issue8446] buildbot: DeprecationWarning not raised for icglue (test_py3kwarn.TestStdlibRemovals)

Ronald Oussoren added the comment: The root cause of this test failure is that test_macos runs before test_py3kwarn. That causes MacOS to be imported before test_py3k runs and that results in not raising the py3k warning by the time test_py3kwarn runs. I propose removing MacOS from the list

[issue8856] Error in ceval.c when building --without-threads

Benjamin Peterson added the comment: Fixed in r81612. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue8856] Error in ceval.c when building --without-threads

Skip Montanaro added the comment: Sorry, forgot the compiler and OS version: i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5490) Mac OSX 10.5.8 S -- ___ Python tracker _

[issue8856] Error in ceval.c when building --without-threads

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

[issue8856] Error in ceval.c when building --without-threads

Skip Montanaro added the comment: Confirmed on Mac OSX. -- nosy: +skip.montanaro ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue8845] Expose sqlite3 connection inTransaction as read-only in_transaction attribute

Changes by R. David Murray : Added file: http://bugs.python.org/file17500/sqlite3_in_transaction.patch ___ Python tracker ___ ___ Python-bugs-l

[issue8845] Expose sqlite3 connection inTransaction as read-only in_transaction attribute

Changes by R. David Murray : Removed file: http://bugs.python.org/file17499/sqlite3_in_transaction.patch ___ Python tracker ___ ___ Python-bugs

[issue8845] Expose sqlite3 connection inTransaction as read-only in_transaction attribute

R. David Murray added the comment: Here is a complete patch, including documentation. I tweaked Shashwat's unit test a bit, and added one to make sure the attribute is read only. I'll apply this soonish if there are no objections. -- assignee: -> r.david.murray stage: unit test need

[issue8748] integer-to-complex comparisons give incorrect results

Mark Dickinson added the comment: Okay, this is now fixed in trunk in r81610, using something closer to your original patch. Thanks for all your help with this! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed _

[issue8797] urllib2 basicauth broken in 2.6.5: RuntimeError: maximum recursion depth exceeded in cmp

chuchiperriman added the comment: The same problem for me, it tries to authenticate infinite times if the user/password are incorrect -- nosy: +chuchiperriman ___ Python tracker ___

[issue8784] tarfile/Windows: Don't use mbcs as the default encoding

Lars Gustäbel added the comment: My expertise on Windows is rather limited, but as far as I understand the issue, I consider this a reasonable idea. I think it is impossible to find a perfect default encoding, and utf-8 seems to be the best bet with regard to portability. IIRC most of the arch

[issue5211] Fix complex type to avoid coercion in 2.7.

Mark Dickinson added the comment: r78280 didn't remove the implicit coercion for rich comparisons; that's now been done in r81606. -- ___ Python tracker ___ ___

[issue8854] msvc9compiler.py: find_vcvarsall() doesn't work with VS2008 on Windows x64

Marc-Andre Lemburg added the comment: Martin v. Löwis wrote: > > Martin v. Löwis added the comment: > > This shouldn't be necessary. If a 32-bit Python looks into the registry, it > will get automatically redirected to Wow6432Node. If a 64-bit Python looks > into the registry, it shouldn't

[issue8748] integer-to-complex comparisons give incorrect results

Mark Dickinson added the comment: Meador, I obviously haven't been thinking clearly about this. Can you think of any reason that we shouldn't just copy the py3k implementation of complex_richcompare wholesale to trunk, with the single modification of replacing "if (PyLong_Check(w))" with "if

[issue8748] integer-to-complex comparisons give incorrect results

Mark Dickinson added the comment: D'oh (again!) [Mark] > Really the coercion for complex types should have been removed at some > point in the 2.x series which of course, it was, in issue 5211. And we should have caught the richcompare coercion in that issue. So I apologise: getting rid of

[issue8623] Aliasing warnings in socketmodule.c

Éric Araujo added the comment: Same with gcc 4.4.4, in socket and another file: Modules/_multiprocessing/multiprocessing.c: In function ‘multiprocessing_sendfd’: Modules/_multiprocessing/multiprocessing.c:125: warning: dereferencing type-punned pointer will break strict-aliasing rules Modules

[issue8856] Error in ceval.c when building --without-threads

Changes by Éric Araujo : -- title: Error in ceval.c when buildind --without-threads -> Error in ceval.c when building --without-threads ___ Python tracker ___ ___

[issue962772] when both maintainer and author provided, author discarded

Éric Araujo added the comment: Tarek, should we change component to Distutils2? -- nosy: +merwok ___ Python tracker ___ ___ Python-b

[issue8856] Error in ceval.c when buildind --without-threads

New submission from Éric Araujo : I can’t build py3k HEAD without threads: $ gcc -v 2>&1 | tail -2 Thread model: posix gcc version 4.4.4 (Debian 4.4.4-1) $ ./configure --without-threads [snip snip] $ make -s Python/ceval.c: In function ‘Py_AddPendingCall’: Python/ceval.c:622: error: request fo

[issue8854] msvc9compiler.py: find_vcvarsall() doesn't work with VS2008 on Windows x64

Martin v. Löwis added the comment: This shouldn't be necessary. If a 32-bit Python looks into the registry, it will get automatically redirected to Wow6432Node. If a 64-bit Python looks into the registry, it shouldn't have any interest in values stored in Wow6432Node. -- nosy: +loewis