[issue3046] Locking should be removed from the new buffer protocol

2008-08-24 Thread Travis Oliphant
Changes by Travis Oliphant <[EMAIL PROTECTED]>: -- status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-lis

[issue3046] Locking should be removed from the new buffer protocol

2008-08-19 Thread Antoine Pitrou
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]> __

[issue3046] Locking should be removed from the new buffer protocol

2008-07-06 Thread Gregory P. Smith
Changes by Gregory P. Smith <[EMAIL PROTECTED]>: -- assignee: -> teoliphant nosy: +gregory.p.smith priority: -> critical ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3046] Locking should be removed from the new buffer protocol

2008-06-06 Thread Travis Oliphant
Travis Oliphant <[EMAIL PROTECTED]> added the comment: Greg Ewing's comment in the thread that read/write locking is orthogonal to memory-buffer moving is to me the most convincing argument that the locking portion of the getbuffer function call should be removed and potentially placed in a separ

[issue3046] Locking should be removed from the new buffer protocol

2008-06-06 Thread Stefan Behnel
Stefan Behnel <[EMAIL PROTECTED]> added the comment: Here is a patch that removes all occurrences of the locking protocol from the current py3k branch code base. There are still some issues in memoryobject.c: - there was an occurrence of PyBUF_SHADOW that might have to be handled - memory_getb

[issue3046] Locking should be removed from the new buffer protocol

2008-06-06 Thread Stefan Behnel
Stefan Behnel <[EMAIL PROTECTED]> added the comment: As a quick summary of the problems with the current PEP: 1) Many use cases will not require any locking at all, either because they run single-threaded with a short-read/short-write pattern, or because they do not write at all. 2) Write locks

[issue3046] Locking should be removed from the new buffer protocol

2008-06-05 Thread Stefan Behnel
New submission from Stefan Behnel <[EMAIL PROTECTED]>: Here is a patch against the current PEP 3118 that removes the LOCK flag. It follows this discussion on the Py3k mailing list: http://comments.gmane.org/gmane.comp.python.python-3000.devel/13409?set_lines=10 It has not yet been approved