Mailing List Archive: [issue1035] bytes buffer API needs to support read locking and/or PyBUF

Mailing List Archive: Python: Bugs
[issue1035] bytes buffer API needs to support read locking and/or PyBUF_LOCKDATA

Index | Next | Previous | View Flat

report at bugs

Sep 11, 2007, 11:57 PM

Views: 92
Permalink

[issue1035] bytes buffer API needs to support read locking and/or PyBUF_LOCKDATA

Gregory P. Smith added the comment:

Attaching the most recent patch (minor update from the second one i sent
to the python-3000 mailing list to initialize ob_readonly_exports = 0 in
the appropriate places).

Current mailing list discussion is pointing out that the name LOCKDATA
means something other than what the existing pep3118 description implies
and that we may want to modify the pep to support more obviously named
things such as READ_LOCK, and EXCLUSIVE or similar... here's a link to
the current thread:

http://mail.python.org/pipermail/python-3000/2007-September/010325.html

----------
keywords: +patch
title: bytes buffer API needs to support PyBUF_LOCKDATA -> bytes buffer API needs to support read locking and/or PyBUF_LOCKDATA

__________________________________
Tracker <report[at]bugs.python.org>
<http://bugs.python.org/issue1035>
__________________________________

Attachments:

bytes-readlock-via-lockdata-gps02.patch.txt (13.0 KB)

Subject	User	Time
[issue1035] bytes buffer API needs to support read locking and/or PyBUF_LOCKDATA	report at bugs	Sep 11, 2007, 11:57 PM

Index | Next | Previous | View Flat

Interested in having your list archived? Contact lists@gossamer-threads.com