Stefan Scherfke

> Basically, `termbg` (if it works as we hope) is going to give us two states: light mode and dark mode. I have a custom script to set/get/toggle darkmode states...

> At some point the datastructures ought to get some documentation. Also I'm planning on expanding out `concurrency.py` with context managers that let you use `asyncio` timeouts and branching in...

Yes, I know that it is not an easy task. I like trio's design for structured concurrency, its API and that it is based on coroutines all the way down....

Aliasing `partial` (e.g., as `P`) can reduce the pain and visual clutter: ```python from functools import partial as P trio.run(P(func, a, b, c=42)) ```

I’ve had a similar issue in typed settings when I want to [updated nested settings](https://gitlab.com/sscherfke/typed-settings/-/blob/main/tests/test_core.py#L121) and fixed it by serializing instances to dicts, calling a [_set_path](https://gitlab.com/sscherfke/typed-settings/-/blob/main/src/typed_settings/_dict_utils.py#L62) function and later converting...

Wat? 👀

`attr.evolve()` can be adjusted relatively easy to work recursively: ```diff diff --git a/src/attr/_funcs.py b/src/attr/_funcs.py index 56e3fcf..1cac98e 100644 --- a/src/attr/_funcs.py +++ b/src/attr/_funcs.py @@ -333,8 +333,13 @@ def evolve(inst, **changes): continue attr_name...

@hynek What are your requirements regarding the public API? Do you prefer a new function or would you rather update the behavior of the existing one as in the diff...

I guess, it’ll be *mostly* backward compatible. *mostly, because handling of nested dicts will be different if they map to attributes with attrs classes. ;-) But the above changes did...

What about packages that build on attrs but add their own wrappers for `attr.s`, `attr.dataclass` or `attr.ib`. Would they need to ship their own plugin for the attrs-mypy-plugin? Or could...