[issue3792] Module variable overridden in child processes with multiprocessing

New submission from Steve Smith <[EMAIL PROTECTED]>: The process variable 'p' is leaking into sub-processes when using the multiprocessing modules. The following code demonstrates the problem: import sys from multiprocessing import Process p = 'Correct' def test(): pri

[issue3640] test_cpickle crash on AMD64 Windows build

Changes by Jesús Cea Avión <[EMAIL PROTECTED]>: -- nosy: +jcea ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing l

[issue3783] dbm.sqlite proof of concept

Changes by Skip Montanaro <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11388/test_dbm_sqlite.py ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3783] dbm.sqlite proof of concept

Changes by Skip Montanaro <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11387/sqlite.py ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3783] dbm.sqlite proof of concept

Changes by Skip Montanaro <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11386/dbm.diff ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3783] dbm.sqlite proof of concept

Skip Montanaro <[EMAIL PROTECTED]> added the comment: OK, I made a sandbox project out of it: svn+ssh://[EMAIL PROTECTED]/sandbox/trunk/dbm_sqlite Hack away! -- assignee: -> skip.montanaro ___ Python tracker <[EMAIL PROTECTED]>

[issue3789] multiprocessing deadlocks when sending large data through Queue with timeout

Jesse Noller <[EMAIL PROTECTED]> added the comment: No problem David, you're the 4th person to ask me about this in the past 2 months :) ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3789] multiprocessing deadlocks when sending large data through Queue with timeout

David Decotigny <[EMAIL PROTECTED]> added the comment: Thank you Jesse. When I read this passage, I thought naively that a timeout raised in a get() would not be harmful: that somehow the whole get() request would be aborted. But now I realize that it would make things rather complicated and dang

[issue3789] multiprocessing deadlocks when sending large data through Queue with timeout

Changes by Jesse Noller <[EMAIL PROTECTED]>: -- resolution: -> invalid status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3789] multiprocessing deadlocks when sending large data through Queue with timeout

Jesse Noller <[EMAIL PROTECTED]> added the comment: In a later release, I'd like to massage this in such a way that you do not have to wait for a child queue to be drained prior to calling join. One way to work around this David, is to call Queue.cancel_join_thread(): def f(datasize, q): q

[issue3789] multiprocessing deadlocks when sending large data through Queue with timeout

Jesse Noller <[EMAIL PROTECTED]> added the comment: See http://docs.python.org/dev/library/multiprocessing.html#multiprocessing- programming Specifically: Joining processes that use queues Bear in mind that a process that has put items in a queue will wait before terminating until all the buff

[issue3791] bsddb not completely removed

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: There are many other places with bsddb. I tried to list all the files here: Doc\library\collections.rst Doc\library\dbm.rst Doc\library\shelve.rst Doc\reference\datamodel.rst Lib\pydoc_topics.py Lib\shelve.py Lib\test\regrtest.py Makefi

[issue3789] multiprocessing deadlocks when sending large data through Queue with timeout

David Decotigny <[EMAIL PROTECTED]> added the comment: A quick fix in the user code, when we are sure we don't need the child process if a timeout happens, is to call worker.terminate() in an except Empty clause. ___ Python tracker <[EMAIL PROTECTED]>

[issue3791] bsddb not completely removed

New submission from Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: Some remnants of the defunct bsddb module, on windows: - _bsddb44.lib is still compiled (but never used anywhere) - _bsddb.py is still referenced by the msi installer This is a release blocker: the installer won't work. -- co

[issue3492] Zlib compress/decompress functions returning bytearray

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: We must definitely clean up other uses of bytearray in the extension modules - see #3790 for an example. ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3790] in zlib decompressor objects, unused_data and unconsumed_tail must be immutable

New submission from Antoine Pitrou <[EMAIL PROTECTED]>: Currently (in py3k), the attributes "unused_data" and "unconsumed_tail" on zlib decompressor objects are bytearrays. This can wreak havoc in the read() method of ZipInfo objects, because one of those bytearrays is assigned to the internal "r

[issue3535] zipfile has problem reading zip files over 2GB

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Fixed in r66240, r66241. Thanks! -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3279] import of site.py fails on startup

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Fixed in r66239. -- resolution: accepted -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3787] Make PyInstanceMethod_Type available or remove it

Christian Heimes <[EMAIL PROTECTED]> added the comment: The issue is no longer a release blocker for the first rc1. Barry has decided against adding instancemethod. However the new tests should be added until the final roles out. -- priority: release blocker -> deferred blocker

[issue3535] zipfile has problem reading zip files over 2GB

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: I also agree with the patch. This seems the correct way to detect the Zip64 format. -- nosy: +amaury.forgeotdarc ___ Python tracker <[EMAIL PROTECTED]>

[issue3787] Make PyInstanceMethod_Type available or remove it

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Usually, when you expose things under _tescapi for testing you test it with related concepts.. I'm not sure what the correct place for this one is, though. (maybe test_class?) Anyway, you could also nest InstanceMethod and testfunction insi

[issue3279] import of site.py fails on startup

Alexandre Vassalotti <[EMAIL PROTECTED]> added the comment: Look good to me, and python-dev accepted the patch. So, go ahead and commit it. -- assignee: -> benjamin.peterson resolution: -> accepted ___ Python tracker <[EMAIL PROTECTED]>

[issue3758] "make check" suggest a testing target under GNU coding standards

Brett Cannon <[EMAIL PROTECTED]> added the comment: On the trunk with r66237 and 3.0 with r66238. -- resolution: -> accepted status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue3660] reference leaks in test_distutils

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: With the new module structure in 3.0, it should be possible to add a cleanup function. It would be a good exercise; I don't know of any module defining such a function. ___ Python tracker <[EMAIL PROT

[issue3279] import of site.py fails on startup

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Yes, indeed. Added file: http://bugs.python.org/file11402/make_modules_builtin2.patch ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3279] import of site.py fails on startup

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: > Windows build files will need to be updated Nothing to do here: they are already built-in, linked into Python30.dll, and listed in PC/config.c But shouldn't the two extension modules be removed from setup.py?

[issue3789] multiprocessing deadlocks when sending large data through Queue with timeout

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- assignee: -> jnoller nosy: +jnoller ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3660] reference leaks in test_distutils

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > It's not only the name, but a copy of the whole module dict just after > import (that's why reload(sys) takes you back the > sys.setdefaultencoding() function). Ow. > Actually I found a (hackish) way to clean the 'extension' dict, but this

[issue3789] multiprocessing deadlocks when sending large data through Queue with timeout

New submission from David Decotigny <[EMAIL PROTECTED]>: With the attached script, then demo() called with for example datasize=40*1024*1024 and timeout=1 will deadlock: the program never terminates. The bug appears on Linux (RHEL4) / intel x86 with "multiprocessing" coming with python 2.6b3 and

[issue3660] reference leaks in test_distutils

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: It's not only the name, but a copy of the whole module dict just after import (that's why reload(sys) takes you back the sys.setdefaultencoding() function). Actually I found a (hackish) way to clean the 'extension' dict, but this is not

[issue3660] reference leaks in test_distutils

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > test_distutils will be difficult; the leak is around the "import xx" in > Lib/distutils/tests/test_build_ext.py. > > And Python/import.c says: > /* To prevent initializing an extension module more than once, we keep a > static dictionary 'e

[issue3660] reference leaks in test_distutils

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: test_distutils will be difficult; the leak is around the "import xx" in Lib/distutils/tests/test_build_ext.py. And Python/import.c says: /* To prevent initializing an extension module more than once, we keep a static dictionary 'extensi

[issue3279] import of site.py fails on startup

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Here's a patch that builds _bytesio and _stringio right into the binary. I think Windows build files will need to be updated, though. -- keywords: +needs review Added file: http://bugs.python.org/file11400/make_modules_builtin.patc

[issue3601] test_unicode.test_raiseMemError fails in UCS4

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Fixed in r66235, r66236. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3660] reference leaks in test_distutils

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: test_distutils is also leaking the the trunk: test_distutils leaked [144, 144, 144, 144] references, sum=576 -- nosy: +benjamin.peterson title: reference leaks in 3.0 -> reference leaks in test_distutils versions: +Python 2.6 ___

[issue3535] zipfile has problem reading zip files over 2GB

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: -- keywords: +needs review ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-lis

[issue3660] reference leaks in 3.0

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Current status: test_distutils leaked [141, 142] references, sum=283 test_logging leaked [0, -219] references, sum=-219 test_smtplib leaked [0, 87] references, sum=87 The distutils leak should be investigated, but the overall situation is ra

[issue3535] zipfile has problem reading zip files over 2GB

Alan McIntyre <[EMAIL PROTECTED]> added the comment: No, I don't have commit access at the moment. ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3535] zipfile has problem reading zip files over 2GB

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Alan, do you have commit access? Otherwise the patch needs approval from another core developer. ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3535] zipfile has problem reading zip files over 2GB

Alan McIntyre <[EMAIL PROTECTED]> added the comment: Your patch seems like a better way to detect whether a file is written as Zip64, and it seems to be able to properly handle extracting a >2GB file from a >2GB archive, so I'd vote to include it. I tested it with r66233, using a file made fro

[issue3279] import of site.py fails on startup

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: IMO, it's unacceptable to be running Python code before the stdio streams are set up. I believe that moving the site initialization after the setting up the streams isn't as big a problem because the dynlibs are on sys.path before site is r

[issue3788] test_cookie isn't comprehensive

New submission from Benjamin Peterson <[EMAIL PROTECTED]>: At the moment, test_cookie only tests SimpleCookie and not completely. It should test Morsel attributes and bad input better. -- components: Library (Lib), Tests keywords: easy messages: 72628 nosy: benjamin.peterson priority: no

[issue3660] reference leaks in 3.0

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: encode-leak3.patch applied in r66234. ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue1638033] Add httponly to Cookie module

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: The patch looks good to me and I will apply it soon if there are not objections. Rewriting of Cookie's tests should probably be another issue. -- assignee: -> benjamin.peterson ___ Python trac

[issue3758] "make check" suggest a testing target under GNU coding standards

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Patch looks fine to me. -- keywords: -needs review ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3574] compile() cannot decode Latin-1 source encodings

Changes by Brett Cannon <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11131/pep3120_test.diff ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3574] compile() cannot decode Latin-1 source encodings

Changes by Brett Cannon <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file11399/test_pep3120.py ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3574] compile() cannot decode Latin-1 source encodings

Changes by Brett Cannon <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11130/fix_latin.diff ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3574] compile() cannot decode Latin-1 source encodings

Brett Cannon <[EMAIL PROTECTED]> added the comment: I have attached a new version of the patch with the changes to test_imp removed as issue 3594 fixed the need for the change. I have also directly uploaded test_pep3120.py since it is flagged as binary and thus cannot be diffed by svn. Added fil

[issue648658] xmlrpc can't do proxied HTTP

djc <[EMAIL PROTECTED]> added the comment: Would this be solved by issue1424152? -- nosy: +djc ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3787] Make PyInstanceMethod_Type available or remove it

Christian Heimes <[EMAIL PROTECTED]> added the comment: Here is a new patch as discussed on IRC. It adds the type to the _testcapi module and the tests to test_capi. Added file: http://bugs.python.org/file11397/instancemethod_capi.patch ___ Python tracker <[E

[issue3787] Make PyInstanceMethod_Type available or remove it

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: It's really to late to add any new features, so adding tests to testcapi seems like the right thing to do. ___ Python tracker <[EMAIL PROTECTED]>

[issue1638033] Add httponly to Cookie module

Matt Chisholm <[EMAIL PROTECTED]> added the comment: I have updated the diff to use reST for the docs. I removed the link to MSDN from the reST docs because it is broken and I could not find the article that it was intended to point to. I also slightly re-worded the paragraph describing httponl

[issue3787] Make PyInstanceMethod_Type available or remove it

New submission from Christian Heimes <[EMAIL PROTECTED]>: A long time ago I added the PyInstanceMethod_Type in r59469. It's a wrapper that turns every function including PyCFunctions into a bindable function. class Example: id = instancemethod(id) Example().id() Without instancemethod the

[issue3785] Can't build ctypes of Python 2.5.2 with Sun Studio 12

Thomas Heller <[EMAIL PROTECTED]> added the comment: The libffi library in Python 2.5 is too old and won't be upgraded to a newer version. I see several possibilities for you: - Use Python 2.6 (if you can live with the beta or wait for the release) - Use Python 2.5, compile with GCC - Use Pyt

[issue3758] "make check" suggest a testing target under GNU coding standards

Brett Cannon <[EMAIL PROTECTED]> added the comment: The attached patch renames the target to patchcheck. -- keywords: +needs review, patch Added file: http://bugs.python.org/file11394/rename_check.diff ___ Python tracker <[EMAIL PROTECTED]>

[issue3776] deprecate bsddb/dbhash in 2.6 for removal in 3.0

Brett Cannon <[EMAIL PROTECTED]> added the comment: Trunk done with r66232 and blocked on 3.0 with r66233. -- resolution: -> accepted status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3769] Deprecate bsddb for removal in 3.0

Brett Cannon <[EMAIL PROTECTED]> added the comment: I accidentally filed this twice, and the code review is on the other issue, so setting the superceder and closing (although the patch has not been applied yet). -- resolution: fixed -> duplicate superseder: -> deprecate bsddb/dbhash in

[issue3623] _json: fix raise_errmsg(), py_encode_basestring_ascii() and linecol()

Senthil <[EMAIL PROTECTED]> added the comment: issue3763 mentions about the similar problem with json library. The traceback posted illustrates the issue (c) mentioned here: File "C:\Python30\lib\json\decoder.py", line 30, in errmsg lineno, colno = linecol(doc, pos) File "C:\Python30\lib

[issue1291446] SSLObject breaks read semantics

Jonathan Ellis <[EMAIL PROTECTED]> added the comment: Ah, great. I was wondering why you kept talking about SSLSocket instead of SSLObject. "New API in 2.6" is good enough for me. Thanks! ___ Python tracker <[EMAIL PROTECTED]>

[issue1040026] os.times() is bogus

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Yes, please move this to 3.0.1 / 2.6.1. The hard part appears to be making sure that it compiles *and* is correct on all conceivable platforms... ___ Python tracker <[EMAIL PROTECTED]>

[issue3162] ssl.SSLSocket implements methods that are overriden by socket.socket.__init__ and methods with incorrect names.

Bill Janssen <[EMAIL PROTECTED]> added the comment: Re: nomenclature I think this is partly a design bug on my part, supporting the old pre-2.6 "read" and "write" methods on the SSL context. Users should really call "makefile" to get something they can "read" and "write"; those methods should,

[issue1291446] SSLObject breaks read semantics

Bill Janssen <[EMAIL PROTECTED]> added the comment: Ah, sorry. I was looking at the 2.6 documentation, not the 2.5 documentation. In 2.6 (which is what the new SSL code is for), documentation of socket.ssl has been removed entirely, along with the text that you cite, although the functionality

[issue3162] ssl.SSLSocket implements methods that are overriden by socket.socket.__init__ and methods with incorrect names.

Simon Cross <[EMAIL PROTECTED]> added the comment: @Bill Janssen: There are currently two patch sets which I think should be applied. For 2.6 it's just trunk-ssl-tests.patch. For 3.0 it's 3k-ssl-methods.patch and 3k-ssl-tests.patch. @Amaury Forgeot d'Arc I agree it's not great nomenclature but

[issue3162] ssl.SSLSocket implements methods that are overriden by socket.socket.__init__ and methods with incorrect names.

Bill Janssen <[EMAIL PROTECTED]> added the comment: Simon, thanks, this patch looks good to me (2.6 only, right?). I'll try it out and report back. If it looks good, I'll commit it. ___ Python tracker <[EMAIL PROTECTED]> __

[issue3162] ssl.SSLSocket implements methods that are overriden by socket.socket.__init__ and methods with incorrect names.

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: I asked this because I find the signature misleading: read(len) or read(buffer, len) io.py, for example, defines read(len) and read_into(buffer). ___ Python tracker <[EMAIL PROTECTED]>

[issue3162] ssl.SSLSocket implements methods that are overriden by socket.socket.__init__ and methods with incorrect names.

Simon Cross <[EMAIL PROTECTED]> added the comment: >> self.read(buf, nbytes) > Shouldn't this function be named readinto()? There is no readinto function (and I suspect one is unlikely to be added now). In Py3k SSLSocket.read takes both len and buffer as optional arguments. ___

[issue1040026] os.times() is bogus

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: I agree with Christian's most recent comment. However without BDFL intervention I think its too late in the 2.6/3.0 release cycle to rush this fix in. It can wait for 2.6.1/3.0.1. I won't have time to look at it for several days myself,

[issue3162] ssl.SSLSocket implements methods that are overriden by socket.socket.__init__ and methods with incorrect names.

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: > self.read(buf, nbytes) Shouldn't this function be named readinto()? -- nosy: +amaury.forgeotdarc ___ Python tracker <[EMAIL PROTECTED]> _

[issue3162] ssl.SSLSocket implements methods that are overriden by socket.socket.__init__ and methods with incorrect names.

Simon Cross <[EMAIL PROTECTED]> added the comment: Test for recv* and send* in 2.6. The tests revealed some bugs so this patch fixes those and supercedes trunk-ssl-methods.patch. Of particular note is that recv_into called self.read(buf, nbytes) which isn't supported in _ssl.c in 2.6. I've work

[issue3783] dbm.sqlite proof of concept

Changes by Gregory Burd <[EMAIL PROTECTED]>: -- nosy: +gregburd ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue3492] Zlib compress/decompress functions returning bytearray

Changes by Jesús Cea Avión <[EMAIL PROTECTED]>: -- nosy: +jcea ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing l

[issue3417] make the fix_dict fixer smarter

Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: I haven't managed to successfully complete the summer of code, due to some personal problems, but I'm still working on 2to3 and on confidence ranking for it. There's a bzr branch with its current implementation at http://isnomore.n

[issue3162] ssl.SSLSocket implements methods that are overriden by socket.socket.__init__ and methods with incorrect names.

Simon Cross <[EMAIL PROTECTED]> added the comment: Tests for recv* and send* methods in 3.0 (2.6 tests coming shortly). Added file: http://bugs.python.org/file11392/3k-ssl-tests.patch ___ Python tracker <[EMAIL PROTECTED]> _

[issue3721] invalid literal for int() with base 16: ''

Changes by Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: -- status: pending -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-

[issue3671] What's New in 2.6 - corrections

A.M. Kuchling <[EMAIL PROTECTED]> added the comment: itertools(product typo fixed in rev. 66231. ___ Python tracker <[EMAIL PROTECTED]> ___ ___ P

[issue3671] What's New in 2.6 - corrections

Chris Lambacher <[EMAIL PROTECTED]> added the comment: In rev66217, the itertools example for "With two iterables, 2N-tuples are returned." has a typo: itertools(product([1,2], [3,4], repeat=2) should be: itertools.product([1,2], [3,4], repeat=2) -- nosy: +lambacck _

[issue3769] Deprecate bsddb for removal in 3.0

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- resolution: rejected -> fixed ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-b

[issue3721] invalid literal for int() with base 16: ''

Eric Smith <[EMAIL PROTECTED]> added the comment: The test fails for me on 2.5.1 (stock Mac OS 10.5.4) in the same way as described in this bug. In 2.6 (r66230) the test succeeds. I recommend we close this. -- nosy: +eric.smith ___ Python tracker <[

[issue3776] deprecate bsddb/dbhash in 2.6 for removal in 3.0

Changes by Jesús Cea Avión <[EMAIL PROTECTED]>: -- nosy: +jcea ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing l

[issue3769] Deprecate bsddb for removal in 3.0

Jesús Cea Avión <[EMAIL PROTECTED]> added the comment: This issue is closed but "rejected". Should it be marked as "accepted" or "fixed"?. ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue1068268] subprocess is not EINTR-safe

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Two remarks: 1 - The part of the patch around the call to select.select() is already in trunk since r64756, almost in the same form. good. 2 - the patch seems to replace all calls to os.write, os.read and os.waipid. But it is based on a

[issue3783] dbm.sqlite proof of concept

Changes by Jesús Cea Avión <[EMAIL PROTECTED]>: -- nosy: +jcea ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing l

[issue3783] dbm.sqlite proof of concept

Skip Montanaro <[EMAIL PROTECTED]> added the comment: Antoine> It would be more efficient to base keys() on iterkeys() than the Antoine> reverse, IMO. True. I was just modifying the dumbdbm implementation. Antoine> Other than that, why not open a branch or at least upload Antoine>

[issue3660] reference leaks in 3.0

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Amaury, your patch is much clearer indeed and it fixes the leak. -- keywords: -needs review ___ Python tracker <[EMAIL PROTECTED]> __

[issue1068268] subprocess is not EINTR-safe

Matteo Bertini <[EMAIL PROTECTED]> added the comment: I'd like to suggest to rise the priority of this bug. Till this bus is around, no way using any module using subprocess.Popen form a PyQt app (and I suppose PyGtk and wxPython too). -- nosy: +naufraghi __

[issue3660] reference leaks in 3.0

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Le vendredi 05 septembre 2008 à 13:08 +, Amaury Forgeot d'Arc a écrit : > Antoine, it seem that with encode-leak2.patch, the error path after > PyErr_WarnEx() leaks the value of "v". Hmm, you are right. > I rewrote the whole paragraph to

[issue874900] threading module can deadlock after fork

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Just checked that the latest patch works on Windows as well. ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3535] zipfile has problem reading zip files over 2GB

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Alan, do you have an opinion on this? -- nosy: +alanmcintyre versions: +Python 2.7, Python 3.1 -Python 2.6, Python 3.0 ___ Python tracker <[EMAIL PROTECTED]>

[issue1757072] Zipfile robustness

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: -- type: -> feature request versions: +Python 2.7, Python 3.1 -Python 2.5 ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3660] reference leaks in 3.0

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Antoine, it seem that with encode-leak2.patch, the error path after PyErr_WarnEx() leaks the value of "v". I rewrote the whole paragraph to make it more straightforward: - the normal case is tested first - all paths end with a "return",

[issue3162] ssl.SSLSocket implements methods that are overriden by socket.socket.__init__ and methods with incorrect names.

Simon Cross <[EMAIL PROTECTED]> added the comment: Attach recvfrom_into method patch for 3.0. Added file: http://bugs.python.org/file11390/3k-ssl-methods.patch ___ Python tracker <[EMAIL PROTECTED]> _

[issue3783] dbm.sqlite proof of concept

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: It would be more efficient to base keys() on iterkeys() than the reverse, IMO. Other than that, why not open a branch or at least upload full-fledged patch files? :) -- nosy: +pitrou ___ Python tra

[issue3162] ssl.SSLSocket implements methods that are overriden by socket.socket.__init__ and methods with incorrect names.

Simon Cross <[EMAIL PROTECTED]> added the comment: I've attached a patch for trunk / 2.6 that adds recv_into and recvfrom_into methods to ssl.SSLSocket and does a minor re-ordering of the nasty lambdas in __init__. The recv_into method is a port of the one from 3.0. The recvfrom_into method is a

[issue3784] Incorrect compiler options used for cc of Sun Studio 12

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Is it really a compile error or just a warning? -- nosy: +pitrou ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3786] _curses, _curses_panel & _multiprocessing can't be build in 2.6b3 w/ SunStudio 12

Michael Schmarck <[EMAIL PROTECTED]> added the comment: Yes, the multiprocessing problem has been fixed by the patch in Issue3110. ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3660] reference leaks in 3.0

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: FWIW, applying encode-leak2.patch removes the leak in test_unicode. ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3776] deprecate bsddb/dbhash in 2.6 for removal in 3.0

Nick Coghlan <[EMAIL PROTECTED]> added the comment: I was actually pretty sure the intention was to add Py3k warnings, but the exact phrase being used in the python-dev thread was "deprecation warnings" which made folks a little nervous. ___ Python tracker <[E

[issue3786] _curses, _curses_panel & _multiprocessing can't be build in 2.6b3 w/ SunStudio 12

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: As for the multiprocessing problem, it has been fixed recently on trunk. Can you give it a try? -- nosy: +pitrou ___ Python tracker <[EMAIL PROTECTED]> __

[issue3492] Zlib compress/decompress functions returning bytearray

Nick Coghlan <[EMAIL PROTECTED]> added the comment: Patch looks good to me (I've only looked at the patch - not the other possible misuses of PyByteArray_ that Amaury noted) -- nosy: +ncoghlan ___ Python tracker <[EMAIL PROTECTED]>

  1   2   >