Message381305
Oh my. FWIW I think that we need to implement this differently. I don't think it matters where, say, an asyncio.Lock was instantiated. It can be created anywhere. So IMO its __init__ shouldn't try to capture the current loop -- there's no need for that. The loop can be and should be captured when the first `await lock.acquire()` is called.
I'm writing a piece of code right now that would need to jump through the hoops to simply create a new `asyncio.Lock()` in a place where there's no asyncio loop yet. |
|
Date |
User |
Action |
Args |
2020-11-17 23:40:09 | yselivanov | set | recipients:
+ yselivanov, asvetlov, aeros |
2020-11-17 23:40:08 | yselivanov | set | messageid: <1605656408.88.0.701899233159.issue42392@roundup.psfhosted.org> |
2020-11-17 23:40:08 | yselivanov | link | issue42392 messages |
2020-11-17 23:40:08 | yselivanov | create | |
|