Matthias Urlichs

Ah, yes, sorry, the real reason `realpath` was added seems to be PyCQA/pylint#791 I'll ask there whether somebody can test this.

The easy way out is to Install [asyncclick](https://pypi.org/project/asyncclick/). Just `import asyncclick as click` and you can use async commands, callbacks and so on as you please. Async coverage should be...

Passing it as a param works in this simple case, but when you build a whole query programmatically …?

@darioackermann Sorry but you're wrong. Building and uploading wheels is easy. Generating them on the client frequently is not, esp. on pseudo-embedded systems with custom Python installations.

> That is, a "code formatter" should only change the whitespace characters in a file while, of course, maintaining the same semantics. Given Python semantics, line length restrictions, and "magic"...

> this issue proposes making that behavior the default. While this issue does propose flipping the `--skip-magic-trailing-comma` flag's default, flipping its default would be quite disruptive and I for one...

OK. Fair enough. Another workable solution to my cargo distribution problem would be partial unload orders, i.e. being able to drop off a given fraction of the load. Even better...

On 28.09.2018 18:28, Jörn Heissler wrote: > |TooSlowError| is especially strange because the timeout wasn't reached. The problem is that `fail_after` cannot discover that it was cancelled manually by yourself...

My use case (close enough): I'm connecting to a host and my connection-setup handshake is protected by a `fail_after` because, well, if that takes too long the host isn't useable....

Yes, that's what I'm seeing. I don't have a test case (a trivial attempt to reproduce this failed) but in my code the `fail_after`'s scope is not even saved.