Message157884
> 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... |
|
Date |
User |
Action |
Args |
2012-04-09 19:31:04 | pitrou | set | recipients:
+ pitrou, georg.brandl, vinay.sajip, r.david.murray, sandro.tosi, docs@python, python-dev, Jim.Jewett |
2012-04-09 19:31:03 | pitrou | link | issue14502 messages |
2012-04-09 19:31:03 | pitrou | create | |
|