Antoine Pitrou <pit...@free.fr> added the comment: > The current question is what contract locks should follow, and whether > all locks should follow it. Would it be acceptable for > logging._releaseLock to raise a RuntimeError if the lock hadn't > previously been acquired?
I don't see the point of this discussion. We are talking about threading.Lock (and, possibly, multiprocessing.Lock), not every lock API under the sun. Especially when it's a private API... ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14502> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
