Roman Zimmermann

@codethief Thanks for finding more examples of this. I’m not sure this is limited to single expressions — although optimizing them would already be a nice improvement! We might want...

I see that there is some trade-off between having exactly one “canonical black” code formatting for every particular file of code on the one side and giving developers control over...

> All of your issues describe providing one timeout for a session rather than how to provide timeouts for requests. In more general terms it’s mostly about pre-configuring request parameters...

> Ignoring the mounds of hate mail I've received for a decision I didn't make I’m really sorry to hear you are getting hate mail for *any* decision made in...

> Remember this lib , is just a user-friendly or elegant HTTP Requests implementation … Exactly. And that’s why it’s worth looking for a user-friendly way to support a very...

Thanks for the quick answer and sorry for dragging this into public. > … I'm not quite ready to abandon it. I’ve not meant for you to abandon the project....

It should work if your JSON would also include the id of the parent model: ```python json_data = {"id": 1, "child": {"id": 1, "name": "new name"}} ```

I see the same here. It seems the app is not compatible with getontracks > 2.0.

Ah nice! There is still the problem that I can either import `regenerator-runtime` or not. If I do it’s also included in the modern output. Can I avoid that somehow?

The code is using both async/await as well as generator functions (`yield *`). Ah, I see. The problem only arises because I wanted *both* the `.js` and the `.modern.js` output...