[issue3598] multiprocessing.Pool windows/linux behaviour difference
New submission from Mark Summerfield [EMAIL PROTECTED]: When the attached program is run on Linux it runs instantly and outputs one line, e.g.: $ python3 mtest.py 100 files, 1702627142 bytes (The number of bytes will vary depending on the system.) When run on Windows XP there is no output at all; many processes seem to be created but nothing seems to actually get done. In both cases I'm using Py30b2. -- components: Library (Lib) files: mtest.py messages: 71408 nosy: mark severity: normal status: open title: multiprocessing.Pool windows/linux behaviour difference versions: Python 3.0 Added file: http://bugs.python.org/file11154/mtest.py ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3598 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3598] multiprocessing.Pool windows/linux behaviour difference
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: There is a problem in your script. On Windows, the remote processes have to import the mtest module, in order to execute the get_size() function. This in turn calls the main() function, which creates a new pool of processes, etc... exponential explosion. Linux forks and does not have this problem. The solution of course is if __name__ == '__main__': main() -- nosy: +amaury.forgeotdarc resolution: - invalid status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3598 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3598] multiprocessing.Pool windows/linux behaviour difference
Antoine Pitrou [EMAIL PROTECTED] added the comment: For what it's worth, this is documented in http://docs.python.org/dev/library/multiprocessing.html#windows -- nosy: +pitrou ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3598 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3598] multiprocessing.Pool windows/linux behaviour difference
Mark Summerfield [EMAIL PROTECTED] added the comment: On 2008-08-19, Antoine Pitrou wrote: Antoine Pitrou [EMAIL PROTECTED] added the comment: For what it's worth, this is documented in http://docs.python.org/dev/library/multiprocessing.html#windows Ah yes, sorry I missed that. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3598 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2394] [Py3k] Finish the memoryview object implementation
Antoine Pitrou [EMAIL PROTECTED] added the comment: Here is a preliminary patch implementing slices with getitem, adding a bunch of tests, and fixing a few problems. As stated elsewhere I only bother to test with simple byte buffers. The semantics of other types of buffers are too fuzzy for me. -- keywords: +patch Added file: http://bugs.python.org/file11155/mem1.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2394 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2834] re.IGNORECASE not Unicode-ready
Barry A. Warsaw [EMAIL PROTECTED] added the comment: I haven't looked at the specific patch, but based on the description of the behavior, I'm +1 on committing this before beta 3. I'm fine with leaving the re.ASCII flags in there -- it will be a marker to indicate perhaps the code needs a closer examination (eventually). -- resolution: - accepted ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2834 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2834] re.IGNORECASE not Unicode-ready
Barry A. Warsaw [EMAIL PROTECTED] added the comment: Make sure of course that the documentation is updated and a NEWS file entry is added. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2834 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2394] [Py3k] Finish the memoryview object implementation
Benjamin Peterson [EMAIL PROTECTED] added the comment: Antoine, if this is a cleanup, perhaps you could fix #3101 while you're at it. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2394 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue898271] symtable module crashes w/ coding declaration
Benjamin Peterson [EMAIL PROTECTED] added the comment: I'm pleased to say this is not an issue in 2.6. -- nosy: +benjamin.peterson resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue898271 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2394] [Py3k] Finish the memoryview object implementation
Antoine Pitrou [EMAIL PROTECTED] added the comment: Here is another patch with setitem too (integers and slices supported), and further tests. Added file: http://bugs.python.org/file11156/mem2.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2394 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue648658] xmlrpc can't do proxied HTTP
Fredrik Lundh [EMAIL PROTECTED] added the comment: It's a missing feature, not a bug in the existing code. But if you're desperate, why not just use the transport implementation that's attached to this issue? ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue648658 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3599] test_pydoc after test_urllib2 causes exception in Popen.__del__
New submission from Benjamin Peterson [EMAIL PROTECTED]:
./python.exe Lib/test/regrtest.py -uall -f ../trunk/tests.txt
test_urllib2
test_pydoc
All 2 tests OK.
Exception TypeError: TypeError('NoneType' object is not callable,) in
bound method Popen.__del__ of subprocess.Popen object at 0x15ffd10
ignored
--
components: Tests
messages: 71422
nosy: benjamin.peterson
priority: high
severity: normal
status: open
title: test_pydoc after test_urllib2 causes exception in Popen.__del__
versions: Python 2.6
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3599
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2394] [Py3k] Finish the memoryview object implementation
Antoine Pitrou [EMAIL PROTECTED] added the comment: This patch fixes a crash in the codecs module. However, memoryview should also support comparisons (just == and !=) with bytes/bytearray objects (or any buffer-enabled objects), otherwise utf-8-sig produces wrong values (and there are no tests for it). Added file: http://bugs.python.org/file11157/mem3.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2394 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Nick Coghlan [EMAIL PROTECTED] added the comment: is_alive appears to be a potentially expensive check for the multiprocessing side of things, which is why I'm inclined to leave it as a method. if t.is_alive(): actually reads better to me than if t.alive: anyway. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Benjamin Peterson [EMAIL PROTECTED] added the comment: On Tue, Aug 19, 2008 at 10:34 AM, Nick Coghlan [EMAIL PROTECTED] wrote: Nick Coghlan [EMAIL PROTECTED] added the comment: is_alive appears to be a potentially expensive check for the multiprocessing side of things, which is why I'm inclined to leave it as a method. if t.is_alive(): actually reads better to me than if t.alive: anyway. So be it. I don't really want to do any renaming anyway. :) ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ -- Cheers, Benjamin Peterson There's no place like 127.0.0.1. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Jesse Noller [EMAIL PROTECTED] added the comment: On Tue, Aug 19, 2008 at 11:34 AM, Nick Coghlan [EMAIL PROTECTED] wrote: Nick Coghlan [EMAIL PROTECTED] added the comment: is_alive appears to be a potentially expensive check for the multiprocessing side of things, which is why I'm inclined to leave it as a method. if t.is_alive(): actually reads better to me than if t.alive: anyway. Dang, I already cut that one over. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3600] Include Tcl/Tk 8.5.4 in the windows binary for the upcoming beta3
New submission from Guilherme Polo [EMAIL PROTECTED]: May I suggest the inclusion of Tcl/Tk 8.5.4 in the windows binary for the upcoming beta3 ? beta2 included 8.5.3, but now the 8.5.4 bugfix release arrived. -- components: Windows messages: 71427 nosy: gpolo severity: normal status: open title: Include Tcl/Tk 8.5.4 in the windows binary for the upcoming beta3 versions: Python 2.6, Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3600 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2394] [Py3k] Finish the memoryview object implementation
Antoine Pitrou [EMAIL PROTECTED] added the comment: Here is a patch to support comparisons of memoryview objects with other objects offering the buffer interface. Two objects are equal if their buffers have the same characteristics and compare equal bytewise. It also improves the test in test_codecs.py, ensuring the problem has been fixed. Added file: http://bugs.python.org/file11158/mem4.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2394 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3601] test_unicode.test_raiseMemError fails in UCS4
New submission from Benjamin Peterson [EMAIL PROTECTED]: == ERROR: test_raiseMemError (test.test_unicode.UnicodeTest) -- Traceback (most recent call last): File /temp/python/trunk/Lib/test/test_unicode.py, line 1122, in test_raiseMemError self.assertRaises(MemoryError, alloc) File /temp/python/trunk/Lib/unittest.py, line 336, in failUnlessRaises callableObj(*args, **kwargs) File /temp/python/trunk/Lib/test/test_unicode.py, line 1121, in lambda alloc = lambda: ua * (sys.maxsize - 100) OverflowError: repeated string is too long -- -- assignee: pitrou messages: 71429 nosy: benjamin.peterson, pitrou priority: critical severity: normal status: open title: test_unicode.test_raiseMemError fails in UCS4 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3601 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2394] [Py3k] Finish the memoryview object implementation
Antoine Pitrou [EMAIL PROTECTED] added the comment: Adding some comparison tests. Added file: http://bugs.python.org/file11159/mem5.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2394 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Nick Coghlan [EMAIL PROTECTED] added the comment: My preference actually isn't particularly strong either way, so I suggest asking Barry for a casting vote. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Jesse Noller [EMAIL PROTECTED] added the comment: Nick/Ben - here's a rough draft patch for the attribute changes for mp - could you both take a look and let me know what you think? -- keywords: +patch Added file: http://bugs.python.org/file11160/mp_api_cleanup.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3601] test_unicode.test_raiseMemError fails in UCS4
Benjamin Peterson [EMAIL PROTECTED] added the comment: Oh. Sorry, I didn't mean to assign it to you anyway. -- assignee: pitrou - ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3601 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3601] test_unicode.test_raiseMemError fails in UCS4
Antoine Pitrou [EMAIL PROTECTED] added the comment: Ok, please disable the test for now, I have more important things to do for the beta :) -- components: +Tests priority: critical - high type: - behavior versions: +Python 2.6, Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3601 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Benjamin Peterson [EMAIL PROTECTED] added the comment: The patch looks pretty good. In a few places, you replaced x.set_x(True) with x.x(True). The docs also will need a few tweaks. Otherwise, if the tests pass, I say go ahead. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3601] test_unicode.test_raiseMemError fails in UCS4
Antoine Pitrou [EMAIL PROTECTED] added the comment: (the fix is probably trivial, it involves dividing sys.maxsize by the number of bytes of an unicode character, something like: width = sys.getsizeof(a) - sys.getsizeof() alloc = lambda: ua * (sys.maxsize // width) self.assertRaises(MemoryError, alloc) self.assertRaises(MemoryError, alloc) you can give it a try if you want ;-)) ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3601 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Nick Coghlan [EMAIL PROTECTED] added the comment: Just saw a couple of docs checkins go by suggesting that the camelCase names will be unavailable in 3.x. Remember that the intent *isn't* to remove the old names from threading.py - we're just adding the PEP 8 names so that multiprocessing can have a PEP 8 compliant API while still being close to a drop-in replacement for the 2.6 version of the threading module. This means that all of the DeprecationWarnings and so forth can be left out completely. Regarding your patch Jesse: - if I remember rightly, get_exitcode() can block waiting for the other process to finish, which makes turning it into a property a fairly questionable idea (p.get_exitcode() blocking is a lot less surprising than p.exitcode doing so) - the get/set documentation for the new properties can probably be consolidated, but that isn't a major problem as far as this week's beta is concerned. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3131] 2to3 can't find fixes_dir
Benjamin Peterson [EMAIL PROTECTED] added the comment: Fixed in r65853. Hopefully we can do the real refactoring fix after the betas. -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3131 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Nick Coghlan [EMAIL PROTECTED] added the comment: Note regarding those comments - only the exitcode one is something we should try to get sorted for the beta. Backing out the deprecation warnings and cleaning up the documentation can wait for the first release candidate. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3046] Locking should be removed from the new buffer protocol
Antoine Pitrou [EMAIL PROTECTED] added the comment: It seems to me that the patch has been applied. Can this be closed? -- nosy: +pitrou ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3046 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3600] Include Tcl/Tk 8.5.4 in the windows binary for the upcoming beta3
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: Also, I was bitten by a runtime error because of an uninitialized variable. It seems that the Microsoft compiler is able to detect uninitialized values, in debug mode this causes a dialog to appear and IDLE crashes when opening the Save file dialog. In generic/tkFileFilter.c, the line 341 if (ostypeCount 0 ostypeList != NULL) should be replaced by if (ostypeList != NULL ostypeCount 0) The problem still exists with 8.5.4. -- nosy: +amaury.forgeotdarc ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3600 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2629] _Py_ForgetReference crash when called from _PyUnicode_New on MemoryError
Antoine Pitrou [EMAIL PROTECTED] added the comment: This should has been fixed by Amaury as part of another patch (the one which is tested for in test_raiseMemError). Could you try again? -- nosy: +pitrou ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2629 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1589] New SSL module doesn't seem to verify hostname against commonName in certificate
Bill Janssen [EMAIL PROTECTED] added the comment: Nope. Hostname verification was never a good idea -- the hostname is just a vague notion, at best -- lots of hostnames can map to one or more IP addresses of the server. It's exposed to the application code, so if a client application wants to do it, it can. But I recommend against it. It's a complication that doesn't belong in the basic support, that is, the SSL module. I'll add a note to this effect in the documentation. -- resolution: - rejected status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1589 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Benjamin Peterson [EMAIL PROTECTED] added the comment: Barry said that is_alive should remain a method following in Guido's footsteps. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3600] Include Tcl/Tk 8.5.4 in the windows binary for the upcoming beta3
Guilherme Polo [EMAIL PROTECTED] added the comment: I don't know what this Microsoft compiler is doing but both ostypeCount and ostypeList are properly set at Tcl_ListObjGetElements, and if that call fails it skips to the bottom of this function you looked at. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3600 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1342811] Tkinter.Menu.delete doesn't delete command of entry
Robert Schuppenies [EMAIL PROTECTED] added the comment: I was thinking about returning in that new if statement, too, but decided not too. The reason is that I didn't want to anticipate _tkinter implementations, which may change (although not likely, still possible). Also, with the third beta tomorrow, I am not sure if somebody will find the time to approve the patch in time. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1342811 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1342811] Tkinter.Menu.delete doesn't delete command of entry
Guilherme Polo [EMAIL PROTECTED] added the comment: If this needs approval of someone else, and such thing doesn't happen in time then the earlier patch should be reverted. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1342811 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3600] Include Tcl/Tk 8.5.4 in the windows binary for the upcoming beta3
Guilherme Polo [EMAIL PROTECTED] added the comment: or not ? the indentation in this tkFileFilter.c is fooling me, the Tcl_ListObjGetElements call is done in another block which is outside that check, so the compiler seems to be right after all. It would be good to report this problem at tk's bug tracker (http://sourceforge.net/projects/tktoolkit). ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3600 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3560] redundant base field in memoryview objects
Guido van Rossum [EMAIL PROTECTED] added the comment: Reviewers: GvR, Message: Looks good. Go ahead and submit, assuming you've run full tests. Description: http://bugs.python.org/issue3560 Please review this at http://codereview.appspot.com/3003 Affected files: Include/memoryobject.h Modules/_json.c Objects/memoryobject.c Objects/unicodeobject.c -- nosy: +gvanrossum ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3560 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3560] redundant base field in memoryview objects
Guido van Rossum [EMAIL PROTECTED] added the comment: PS. The PEP probably needs an update. And the docs. http://codereview.appspot.com/3003 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3560 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3560] redundant base field in memoryview objects
Guido van Rossum [EMAIL PROTECTED] added the comment: On 2008/08/19 17:18:45, GvR wrote: PS. The PEP probably needs an update. And the docs. And Misc/NEWS http://codereview.appspot.com/3003 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3560 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3554] ctypes.wstring_at and string_at call Python API without the GIL
Thomas Heller [EMAIL PROTECTED] added the comment: This is fixed now in SVN, in trunk, branches/py3k, and branches/release25-maint. Thanks again. -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3554 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3265] Python-2.5.2/Modules/_ctypes/malloc_closure.c:70: error: `MAP_ANONYMOUS' undeclared
Thomas Heller [EMAIL PROTECTED] added the comment: Here is a patch for Modules/_ctypes/malloc_closure.c that may work (totally untested). The code snippet is copied from Modules/mmapmodule.c. -- keywords: +patch Added file: http://bugs.python.org/file11161/malloc_closure.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3265 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3265] Python-2.5.2/Modules/_ctypes/malloc_closure.c:70: error: `MAP_ANONYMOUS' undeclared
Thomas Heller [EMAIL PROTECTED] added the comment: Corrected the patch. Added file: http://bugs.python.org/file11162/malloc_closure.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3265 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3265] Python-2.5.2/Modules/_ctypes/malloc_closure.c:70: error: `MAP_ANONYMOUS' undeclared
Changes by Thomas Heller [EMAIL PROTECTED]: Removed file: http://bugs.python.org/file11161/malloc_closure.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3265 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Jesse Noller [EMAIL PROTECTED] added the comment: Nick Coghlan [EMAIL PROTECTED] added the comment: Note regarding those comments - only the exitcode one is something we should try to get sorted for the beta. Backing out the deprecation warnings and cleaning up the documentation can wait for the first release candidate. Would it be acceptable to add a doc note mentioning .exitcode() may block rather than changing it back to the get_exitcode method? It's not that it's hard - but I do like the consistency of the property-style interface. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2619] Document PEP 3118
Antoine Pitrou [EMAIL PROTECTED] added the comment: As a reminder, I want to mention that PEP 3118 itself needs to be updated (see #3560). -- nosy: +pitrou ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2619 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3560] redundant base field in memoryview objects
Antoine Pitrou [EMAIL PROTECTED] added the comment: Well, the PEP needs some love generally speaking; many things are un- or under-specified (and I don't understand better than anyone else). As for docs, there aren't any (grep -ri memoryview Doc/ yields only the two lines referencing the memoryview builtin): see #2619. The patch is committed in r65862. -- resolution: accepted - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3560 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2834] re.IGNORECASE not Unicode-ready
Antoine Pitrou [EMAIL PROTECTED] added the comment: Fixed in r65860. Someone should check the docs though (at least try to generate them, and review my changes a bit since English isn't my mother tongue). -- resolution: accepted - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2834 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3602] Move test.test_suport.catch_warning() to the 'warnings' module
New submission from Brett Cannon [EMAIL PROTECTED]: Since most UNIX distros don't ship Python's test directory, test.test_support.catch_warning() needs to be moved to the 'warnings' directory so it can be used to suppress warnings in modules outside the 'test' package. The default for 'record' will change to False so it is less test-oriented. The name might change as well since it is more about saving the state of 'warnings' then actually catching an exception, although having it return an object representation of a warning makes the current name make sense. -- assignee: brett.cannon components: Library (Lib) messages: 71459 nosy: brett.cannon priority: critical severity: normal status: open title: Move test.test_suport.catch_warning() to the 'warnings' module type: behavior versions: Python 2.6, Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3602 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Jesse Noller [EMAIL PROTECTED] added the comment: Nick Coghlan [EMAIL PROTECTED] added the comment: Note regarding those comments - only the exitcode one is something we should try to get sorted for the beta. Backing out the deprecation warnings and cleaning up the documentation can wait for the first release candidate. Actually, re-examining .exitcode - it wraps the custom forking.Popen class .poll() method, this method should not block (forking.py, line 104) - the WNOHANG call passed to os.waitpid means it should also not hang. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Jesse Noller [EMAIL PROTECTED] added the comment: Here is a cleaned up patch (ben was right, I typo'ed a few spots) - I did not clean up the docs from the original patch except to correct the x.x(Foo) accidents. Added file: http://bugs.python.org/file11163/mp_nohang_jnoller.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Changes by Jesse Noller [EMAIL PROTECTED]: Removed file: http://bugs.python.org/file11160/mp_api_cleanup.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Changes by Jesse Noller [EMAIL PROTECTED]: Removed file: http://bugs.python.org/file11163/mp_nohang_jnoller.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Jesse Noller [EMAIL PROTECTED] added the comment: I attached the wrong patch, here is v2 Added file: http://bugs.python.org/file11164/mp_api_cleanup.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Jesse Noller [EMAIL PROTECTED] added the comment: And here is v3 - I fixed all of the Docs/include/mp* scripts to reflect the new API Added file: http://bugs.python.org/file11165/mp_api_cleanup-v3.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3352] Deficiencies in multiprocessing/threading API
Jesse Noller [EMAIL PROTECTED] added the comment: committed the v3 patch as-is in r65864 - moving from release blocker to deferred blocker pending the Docs cleanup, and outstanding debate points. -- priority: release blocker - deferred blocker ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3603] trivial typo in Include/pymath.h
New submission from Santiago Gala [EMAIL PROTECTED]: file Include/pymath.h has the typo s/doube/double/, hidden by the fact that any sane OS defines copysign: diff --git a/Include/pymath.h b/Include/pymath.h index a3735c2..7cea9ae 100644 --- a/Include/pymath.h +++ b/Include/pymath.h @@ -19,7 +19,7 @@ functions and constants *Note: PC/pyconfig.h defines copysign as _copysign */ #ifndef HAVE_COPYSIGN -extern double copysign(doube, double); +extern double copysign(double, double); #endif #ifndef HAVE_ACOSH It is both in trunk and py3k -- messages: 71465 nosy: sgala severity: normal status: open title: trivial typo in Include/pymath.h type: compile error ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3603 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1878] class attribute cache failure (regression)
Guido van Rossum [EMAIL PROTECTED] added the comment: I like Armin's latest proposal: have Py_TPFLAGS_DEFAULT include Py_TPFLAGS_HAVE_VERSION_TAG when compiling the core only. ISTR there's a way to do this, but I can't find it right now. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1878 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2394] [Py3k] Finish the memoryview object implementation
Antoine Pitrou [EMAIL PROTECTED] added the comment: This patch changes all bytearray results (in indexing, tobytes()) to bytes, and adds the implementation the tolist(). Note: the tolist() implementation only handles one-dimensional byte buffers. It will have to be re-written using the struct module! But at least once that patch applied, I think we may drop down this bug to critical. Added file: http://bugs.python.org/file11166/mem6.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2394 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1878] class attribute cache failure (regression)
Guido van Rossum [EMAIL PROTECTED] added the comment: Please review the patch here: http://codereview.appspot.com/3005 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1878 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2394] [Py3k] Finish the memoryview object implementation
Antoine Pitrou [EMAIL PROTECTED] added the comment: Please review at http://codereview.appspot.com/3004 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2394 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3603] trivial typo in Include/pymath.h
Benjamin Peterson [EMAIL PROTECTED] added the comment: Thanks! Fixed in r65869. -- nosy: +benjamin.peterson resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3603 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Barry A. Warsaw [EMAIL PROTECTED] added the comment: Guido's approved it, so please go ahead and add it before beta 3. -- resolution: - accepted ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3604] broken link in curses module docs
New submission from Matt Beaumont-Gay [EMAIL PROTECTED]: The link to the Curses Programming with Python page on the curses module doc page (http://www.python.org/doc/lib/module-curses.html) is broken; the correct link is apparently 'http://docs.python.org/dev/howto/curses.html'. -- assignee: georg.brandl components: Documentation messages: 71472 nosy: georg.brandl, mattb severity: normal status: open title: broken link in curses module docs versions: Python 2.5 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3604 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Benjamin Peterson [EMAIL PROTECTED] added the comment: Applied for 2.6 in r65872. -- status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue815646] thread unsafe file objects cause crash
Gregory P. Smith [EMAIL PROTECTED] added the comment: The fix can not be committed to Python 2.5 because it breaks compatibility by adding another field to the PyFileObject struct and adding two new C API functions. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue815646 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2629] _Py_ForgetReference crash when called from _PyUnicode_New on MemoryError
Gregory P. Smith [EMAIL PROTECTED] added the comment:
Verified fixed.
Python 2.6b2+ (trunk:65871, Aug 19 2008, 13:10:07)
msg = 'A'*2000111222
[12389 refs]
x = msg.decode('utf8')
Traceback (most recent call last):
File stdin, line 1, in module
File /usr/local/google/home/gps/python/trunk/Lib/encodings/utf_8.py,
line 16, in decode
return codecs.utf_8_decode(input, errors, True)
MemoryError
[12431 refs]
--
assignee: - gregory.p.smith
priority: - normal
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2629
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1878] class attribute cache failure (regression)
Guido van Rossum [EMAIL PROTECTED] added the comment: Submitted as r65874. I will block this for 3.0; 3.0 extensions that want to mess with tp_dict must explicitly disable this flag. -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1878 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1179] [CVE-2007-4965] Integer overflow in imageop module
Guido van Rossum [EMAIL PROTECTED] added the comment: Looking into this now. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1179 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3605] Py_FatalError causes infinite loop
New submission from Roger Upole [EMAIL PROTECTED]: Py_FatalError calls PyErr_Occurred() which requires a current thread state. This mean that if the original error was a thread state error Py_FatalError is triggered again, ad infinitum. -- components: Interpreter Core messages: 71478 nosy: rupole severity: normal status: open title: Py_FatalError causes infinite loop versions: Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3605 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1878] class attribute cache failure (regression)
Benjamin Peterson [EMAIL PROTECTED] added the comment: Do we want a test? ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1878 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3139] bytearrays are not thread safe
Antoine Pitrou [EMAIL PROTECTED] added the comment: Le samedi 16 août 2008 à 05:50 +, Ismail Donmez a écrit : This seems to break test_unicode on MacOSX 10.5.4, test_unicode python(80320,0xa0659fa0) malloc: *** mmap(size=2147483648) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug python(80320,0xa0659fa0) malloc: *** mmap(size=2147483648) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug Can you run Lib/test/test_unicode.py directly to know which test precisely crashes? ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3139 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Benjamin Peterson [EMAIL PROTECTED] added the comment: Done for py3k in r65877. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3453] PyType_Ready doesn't ensure that all bases are ready
Roger Upole [EMAIL PROTECTED] added the comment: This doesn't address the discrepancy between tp_base and tp_bases. If multiple bases are used, it's no longer 'good practice', it's an absolute requirement. IMO, it should call PyType_Ready for all bases, or none of them. Since the code assumes that all bases have been initialized, it could at least ASSERT so, rather than crashing deep within the mro calculations. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3453 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1179] [CVE-2007-4965] Integer overflow in imageop module
Guido van Rossum [EMAIL PROTECTED] added the comment: Latest patches applied to 2.5 branch: r65878. And to 2.6 trunk: r65880. -- resolution: - accepted status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1179 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1878] class attribute cache failure (regression)
Guido van Rossum [EMAIL PROTECTED] added the comment: Sure, go right ahead. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1878 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3605] Py_FatalError causes infinite loop
Antoine Pitrou [EMAIL PROTECTED] added the comment: Do you have a simple code sample to showcase that? -- nosy: +pitrou ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3605 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Benjamin Peterson [EMAIL PROTECTED] added the comment: Now test_compiler is breaking for us because the compiler package can't handle the change. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3605] Py_FatalError causes infinite loop
Roger Upole [EMAIL PROTECTED] added the comment: Py_BEGIN_ALLOW_THREADS PyErr_SetString(PyExc_SystemError, bork bork bork); Py_END_ALLOW_THREADS ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3605 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3605] Py_FatalError causes infinite loop
Antoine Pitrou [EMAIL PROTECTED] added the comment: Roger Upole [EMAIL PROTECTED] added the comment: Py_BEGIN_ALLOW_THREADS PyErr_SetString(PyExc_SystemError, bork bork bork); Py_END_ALLOW_THREADS Well, if you start using all kinds of internal APIs without holding the GIL, you should expect much worse than just a Py_FatalError ;-) Of course, it would still be better if the infinite loop could be avoided. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3605 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3605] Py_FatalError causes infinite loop
Roger Upole [EMAIL PROTECTED] added the comment: Well, you asked for a simple case. In practice, I'm dealing with much more complicated code that contains callbacks which may need to acquire or release the theadlock. This problem makes it very difficult to debug such code. Also, the PyErr_Occurred is not present in 2.5.2, probably for this very same reason. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3605 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3605] Py_FatalError causes infinite loop
Changes by Daniel Diniz [EMAIL PROTECTED]: -- nosy: +ajaksu2 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3605 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3606] 2to3: commands varible replaced by subprocess
New submission from STINNER Victor [EMAIL PROTECTED]: I tried 2to3 on my python-ptrace project and with minor changes, it works fine. One of the minor changes is to replace subprocess.split(;) by commands.split(;). The original code was: commands = command ok = True for command in commands.split(;): command = command.strip() ok = self.execute(command) I don't import subprocess and I don't use this module in my code. It is possible to reproduce the bug only with two lines: commands = a;b;c x = commands.split(;) So 2to3 doesn't care if commands is a module or variable, it just replaced the text pattern... It looks like the change is done by fixes/fix_imports.py, maybe this pattern: # Find usages of module members in code e.g. urllib.foo(bar) yield power (%s) trailer'.' any any* % mod_name_list -- assignee: collinwinter components: 2to3 (2.x to 3.0 conversion tool) messages: 71490 nosy: collinwinter, haypo severity: normal status: open title: 2to3: commands varible replaced by subprocess ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3606 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3606] 2to3: commands varible replaced by subprocess
Benjamin Peterson [EMAIL PROTECTED] added the comment: Yes, this is because some of the commands module's functions have moved to subprocess in py3k. This is probably a won't fix. -- nosy: +benjamin.peterson ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3606 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3607] test_multiprocessing failure (Unserializable message)
New submission from Antoine Pitrou [EMAIL PROTECTED]:
I have the following deterministic failure on py3k:
test test_multiprocessing failed -- Traceback (most recent call last):
File /home/antoine/py3k/__svn__/Lib/test/test_multiprocessing.py,
line 932, in test_dict
self.assertEqual(sorted(d.keys()), indices)
File string, line 2, in keys
File /home/antoine/py3k/__svn__/Lib/multiprocessing/managers.py,
line 738, in _callmethod
raise convert_to_error(kind, result)
multiprocessing.managers.RemoteError:
---
Unserializable message: ('#RETURN', dict_keys object at 0x956ddb0)
---
--
assignee: jnoller
components: Library (Lib), Tests
messages: 71492
nosy: jnoller, pitrou
priority: critical
severity: normal
status: open
title: test_multiprocessing failure (Unserializable message)
type: behavior
versions: Python 3.0
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3607
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2394] [Py3k] Finish the memoryview object implementation
Antoine Pitrou [EMAIL PROTECTED] added the comment: Committed in r65886 after review from Benjamin and some small fixes. I'm downgrading this to critical for the remains of the memoryview API (support for more format types, multi-dimensional objects...). Perhaps those remainings will have to wait for 3.1. -- priority: release blocker - critical ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2394 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3608] memoryview constructor has no deallocator
New submission from Roger Upole [EMAIL PROTECTED]: When using PyMemoryView_FromMemory to create a new object, you have to pass in a preallocated buffer. However, there's no way to specify a routine to free the memory, and it leaks when the object is destroyed. -- components: Interpreter Core messages: 71495 nosy: rupole severity: normal status: open title: memoryview constructor has no deallocator type: resource usage versions: Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3608 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3402] test_nis is hanging on Solaris
Benjamin Peterson [EMAIL PROTECTED] added the comment: Ok. I've disabled it in r65888. -- priority: release blocker - critical ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3402 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3608] memoryview constructor has no deallocator
Roger Upole [EMAIL PROTECTED] added the comment: Well it existed up until a couple hours ago ;). Looks like it was recently changed to PyMemoryView_FromBuffer. However, it still has the same issue. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3608 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3608] memoryview constructor has no deallocator
Changes by Benjamin Peterson [EMAIL PROTECTED]: -- assignee: - teoliphant nosy: +pitrou, teoliphant ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3608 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3318] Documentation: timeit: lower bound should read upper bound
unutbu [EMAIL PROTECTED] added the comment: Dear Georg, Would you please reconsider this issue (http://bugs.python.org/issue3318) for a moment? The term lower bound as it is used in the timeit documentation is either misleading or mathematically incorrect. A lower bound is a number which is less than or equal to every member of a set. What set is the timeit documentation referring to? Here are two possibilities: A = the set of times recorded from three runs B = the set of all possible times a particular machine could return The term lower bound is technically correct if the documentation means lower bound of set A, but I think it would be misleading to use the term lower bound in this way, since the documentation would then be asserting: the minimum time of three runs is the lower bound of three runs. It's not very exciting, and moreover, it's obvious. The term lower bound is simply incorrect if the documentation meant lower bound of set B. I explained the reason why in my first post. I appreciate your point when you said, An ideal machine is not useful in practice. However, the documentation opens up this can of worms by its own use of the term lower bound. If ideal machines is not what it wants to discuss, then maybe the documentation needs to be changed in some other way to avoid the mathematically charged term, lower bound. I think you would agree that good documentation needs to use language accurately. The documentation as it stands is either fallacious (if it is talking about set B), trivial (if it is talking about set A), or possibly correct if it is talking about some set C which I have not imagined. If it is the latter case, please update the documentation to make clear what set C is. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3318 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3609] does parse_header really belong in CGI module?
New submission from Bill Janssen [EMAIL PROTECTED]: Not sure how to class this, but shouldn't the parse_header function in cgi really be in email.header? And what about parse_multipart? -- components: Library (Lib) messages: 71500 nosy: janssen priority: normal severity: normal status: open title: does parse_header really belong in CGI module? type: feature request versions: Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3609 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3139] bytearrays are not thread safe
Ismail Donmez [EMAIL PROTECTED] added the comment: Can you run Lib/test/test_unicode.py directly to know which test precisely crashes? The latest py3k branch is fine now and the test passes. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3139 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3611] invalid exception context
New submission from STINNER Victor [EMAIL PROTECTED]:
After few seconds (30 sec to 5 minutes), my program (Fusil) crashs at:
PyEval_EvalFrameEx (f=0x85b4324, throwflag=0) at Python/ceval.c:2459
Py_CLEAR(tstate-exc_traceback);
It crashs because tstate-exc_traceback points to a zombi object:
{_ob_next = 0xdbdbdbdb, _ob_prev = 0xdbdbdbdb, ob_refcnt = -606348326,
ob_type = 0xdbdbdbdb}
(refcnt is 0xdbdbdbdb-1)
I'm using py3k rev 65882 compiled with CFLAGS -O0 -ggdb
and --with-pydebug. Sorry, I don't have more informations yet and I
can't explain how to reproduce the bug :-/
--
components: Interpreter Core
messages: 71503
nosy: haypo
severity: normal
status: open
title: invalid exception context
type: crash
versions: Python 3.0
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3611
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3607] test_multiprocessing failure (Unserializable message)
Benjamin Peterson [EMAIL PROTECTED] added the comment: Here's a buildbot example: http://python.org/dev/buildbot/stable/amd64%20gentoo%203.0/builds/980/step-test/0 -- nosy: +benjamin.peterson ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3607 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3611] invalid exception context
STINNER Victor [EMAIL PROTECTED] added the comment: The crash is on ProcError exception raising (line 21): 20 except IOError as err: 21 raise ProcError(Unable to open %r: %s % (filename, --- (gdb) where #0 0x0805bcc7 in PyObject_Hash (v=0x8691034) at Objects/object.c:796 #1 0x08062125 in set_contains_key (so=0x856ec6c, key=0x8691034) at Objects/setobject.c:682 #2 0x0806659f in PySet_Contains (anyset=0x856ec6c, key=0x8691034) at Objects/setobject.c:2263 #3 0x080def3a in print_exception_recursive (f=0xb7bea654, value=0x8656814, seen=0x856ec6c) at Python/pythonrun.c:1432 #4 0x080df0ea in PyErr_Display (exception=0x84542ac, value=0x8656814, tb=0x865bc34) at Python/pythonrun.c:1470 #5 0x080e68f6 in sys_excepthook (self=0xb7e013b4, args=0x865b334) at Python/sysmodule.c:119 #6 0x08161d29 in PyCFunction_Call (func=0xb7e016c4, arg=0x865b334, kw=0x0) at Objects/methodobject.c:81 #7 0x08118cc5 in PyObject_Call (func=0xb7e016c4, arg=0x865b334, kw=0x0) at Objects/abstract.c:2181 #8 0x080b2ea8 in PyEval_CallObjectWithKeywords (func=0xb7e016c4, arg=0x865b334, kw=0x0) at Python/ceval.c:3283 #9 0x080de463 in PyErr_PrintEx (set_sys_last_vars=1) at Python/pythonrun.c:1258 #10 0x080de06f in PyErr_Print () at Python/pythonrun.c:1150 #11 0x080e0007 in Py_FatalError (msg=0xbf9a1498 Python/ceval.c:2459 object at 0x865b6b4 has negative ref count -606348326) at Python/pythonrun.c:1863 #12 0x0805a821 in _Py_NegativeRefcount (fname=0x8197098 Python/ceval.c, lineno=2459, op=0x865b6b4) at Objects/object.c:194 #13 0x080b004f in PyEval_EvalFrameEx (f=0x85b4324, throwflag=0) at Python/ceval.c:2459 (...) (gdb) frame 13 #13 0x080b004f in PyEval_EvalFrameEx (f=0x85c9794, throwflag=0) at Python/ceval.c:2459 2459 Py_CLEAR(tstate-exc_traceback); (gdb) pystack /home/haypo/ptrace/ptrace/linux_proc.py (21): openProc /home/haypo/ptrace/ptrace/linux_proc.py (24): readProc /home/haypo/ptrace/ptrace/linux_proc.py (31): readProcessProc /home/haypo/ptrace/ptrace/linux_proc.py (74): readProcessStat (...) --- linux_proc.py code near line 21: (...) 7 class ProcError(Exception): 8 pass (...) 16 def openProc(path): 17 try: 18 filename = procFilename(path) 19 return open(filename) 20 except IOError as err: 21 raise ProcError(Unable to open %r: %s % (filename, err)) (...) 29 def readProcessProc(pid, key): 30 try: 31 return readProc(path_join(str(pid), str(key))) 32 except ProcError as error: 33 raise ProcError(Process %s doesn't exist: %s % ( 34 pid, error)) (...) 73 def readProcessStat(pid): 74 stat = readProcessProc(pid, 'stat') 75 return ProcessState(stat) 76 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3611 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3611] invalid exception context
STINNER Victor [EMAIL PROTECTED] added the comment:
I also noticed a crash in PyErr_SetObject(): in block line 68..86,
tstate-exc_value value may changes and so it's possible that
tstate-exc_value becomes NULL. I added a test to avoid this crash:
Index: Python/errors.c
===
--- Python/errors.c (révision 65899)
+++ Python/errors.c (copie de travail)
@@ -88,7 +88,7 @@
This is O(chain length) but context chains are
usually very short. Sensitive readers may try
to inline the call to PyException_GetContext. */
- if (tstate-exc_value != value) {
+ if (tstate-exc_value != value tstate-exc_value !=
NULL) {
PyObject *o = tstate-exc_value, *context;
while ((context = PyException_GetContext(o)))
{
Py_DECREF(context);
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3611
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue658693] cPickle does relative import
Benjamin Peterson [EMAIL PROTECTED] added the comment: Is this still an issue? -- nosy: +benjamin.peterson ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue658693 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue515073] subtypable weak references
Benjamin Peterson [EMAIL PROTECTED] added the comment: Does anyone still care about this? -- nosy: +benjamin.peterson ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue515073 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
