Matthias Urlichs

> a `RandomAccessFile` that only exposes the equivalents of `pread` and `pwrite`. plus `append`, please. @richardsheridan Putting these into a thread might not help if the code in question doesn't...

Append mode also has the problem that `pwrite64` ignores your offset, it *always* appends. Not a good idea. Personally I'd prefer the "call stat plus use file locking" approach if...

> I guess technically you can use io_uring with an epoll loop by doing something tricky with eventfd, Yeah, just as technically you can emulate a 32-bit CPU with an...

This code looks like it should work, so I'd prefer the latter solution.

Yes, `poison` as an exception-on-the-other-side-raising alternate to closing would be useful. (Maybe just add an appropriate argument to `.close`?)

On 11.01.19 02:31, Nathaniel J. Smith wrote: > > Not super eager to rename things again, but I'm still mixing them up > on a regular basis :-(. > We...

Explicit is better than implicit: If you want to use a channel in more than one task independently, clone it. Yes, "async with:" should close its resource. Files also get...

Uh, it may be benign but it's really blowing up our tracebacks. This is a comparatively simple example, you can easily build one where the real problem is buried in...

Hmm. I think you're conflating two orthogonal tasks here: - detect a deadlock - add a timeout to a task The latter is easy, of course: ```python def run_task(afn, args,...

> different use cases that unlock with an asynchronous API such as `Future` Yeah, that's one of the problems with asyncio's Futures. They conflate a heap of different usecases into...