[issue1028] Tkinter binding involving Control-spacebar raises unicode error

gumpy added the comment: 8.5.0 This is still an issue with both tk versions in the 3.0.1 python release. ___ Python tracker <http://bugs.python.org/issue1028> ___ ___

[issue4840] Compile dbm in Ubuntu

gumpy added the comment: I believe this is already fixed. #4483 -- nosy: +gumpy ___ Python tracker <http://bugs.python.org/issue4840> ___ ___ Python-bugs-list m

[issue4509] bugs in array.array with exports (buffer protocol)

gumpy <[EMAIL PROTECTED]> added the comment: I've opened a new memoryview/array segfault issue since #4569 was closed: #4583 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.

[issue4583] segfault when mutating memoryview to array.array when array is resized

New submission from gumpy <[EMAIL PROTECTED]>: This is with r67651 and related to #4569, #4509 and possibly #4580. >>> from array import array >>> a = array('i', range(16)) >>> m = memoryview(a) >>> a.extend(array('i', range(48)))

[issue4572] add SEEK_* values to io and/or io.IOBase

New submission from gumpy <[EMAIL PROTECTED]>: Currently io.IOBase.seek(offset[, whence]) uses magic numbers for the second argument. Since this is essentially identical the C function fseek I think adding the same "constants" that C uses (SEEK_SET=0, SEEK_CUR=1, SEEK_END

[issue1028] Tkinter binding involving Control-spacebar raises unicode error

gumpy <[EMAIL PROTECTED]> added the comment: This problem exists for me on Ubuntu8.04 with both tk/tcl8.4.16 and 8.5. -- nosy: +gumpy ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue4509] possible memoryview bug

gumpy <[EMAIL PROTECTED]> added the comment: It turns out the problems in array are more serious than I thought and allow writing to unallocated memory through a memoryview leading to memory corruption, segfaults and possibly exploits. The following example extends an array enough to tri

[issue4509] bugs in bytearray with exports (buffer protocol)

gumpy <[EMAIL PROTECTED]> added the comment: I've found that arrays from the array module have similar issues: >>> a = array.array('i', range(2)) >>> m = memoryview(a) >>> bytes(m) b'\x00\x00\x00\x00\x01\x00\x00\x00' >

[issue4509] bugs in bytearray with exports (buffer protocol)

gumpy <[EMAIL PROTECTED]> added the comment: Sorry, forgot to give this issue a more accurate title earlier. -- title: possible memoryview bug -> bugs in bytearray with exports (buffer protocol) ___ Python tracker <[EMAIL PROTE

[issue4509] possible memoryview bug

gumpy <[EMAIL PROTECTED]> added the comment: I found another related bug. In bytes_setslice, when the buffer is resized to a smaller size, a memmove happens regardless of whether the resize is successful or not. >>> b = bytearray(range(10)) >>> m = memoryview(b) >

[issue4537] webbrowser.UnixBrowser should use builtins.open

gumpy <[EMAIL PROTECTED]> added the comment: I'd suggest the same thing that was done on lines 351-352. Index: Lib/webbrowser.py === --- Lib/webbrowser.py (revision 67538) +++ Lib/webbrowser.py (working copy) @@ -2

[issue4509] possible memoryview bug

New submission from gumpy <[EMAIL PROTECTED]>: I'm unsure of the expected behavior in this case but it seems odd. The bytearray in the following example can be resized to a length of 5-10 bytes without throwing an exception. Python 3.0rc3 (r30rc3:67312, Dec 3 2008, 10:38:14)