Antoine Pitrou added the comment: Ok, since we're bikeshedding, I like Richard's proposal best:
> Personally, I would prefer to make the shared and exclusive locks > attributes of the same object, so one could do > > with selock.shared: > ... > > with selock.exclusive: > ... Please note, the "same object" could simply be a namedtuple instance. Also I think "shared/exclusive" indeed conveys the semantics better than "read/write". ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8800> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
