Max R

I would also be interested in support for showing the next N arrivals. Happy to submit PR's for this once we agree on what the YAML/API should look like

Currently values under `options.extra_requires` get rendered as lists. Should `dev` be special-cased?

Sorry nevermind, `dev` is just an arbitrary name. I realize the issue is in this part of the code https://github.com/asottile/setup-cfg-fmt/blob/acc732d13a11c70e23f887586060c1ee28e0d7f7/setup_cfg_fmt.py#L222-L238 but it's not clear what the right behavior is supposed...

I think this problem is agnostic to this integration. See https://community.home-assistant.io/t/how-to-delete-sensor-entity-that-was-defined-in-the-configuration-yaml-before/417112 and https://community.home-assistant.io/t/removing-sensor-permanently-and-or-deleting-historic-data/484979 for some things to try

Instructions to rename the binary are already documented at https://github.com/nferraz/st/blob/915674e31bea860345c4980bef1dc6a955757cb4/INSTALL#L10-L21 It's not helpful or polite to phrase your issue as "Can I have them both [...] No I can't. So...

It seems this issue was resolved by #196

Thanks Teemu. Will try to find some time to dive into the code and implementation before year-end.

Makes sense

Apologies, I was unable to review this before the New Year and I'm not sure I have the availability to work on it soon.

> Glad you got it working, and thanks a lot for reporting back! I think you're confusing @MaxRower and me 😅