What helps a lot for apps with multiple config files:

• if you tell the user to “add code xy to the config file” : tell me which file. is it the main config file? the one of the reverse proxy etc.?
• provide a sensible example library of the config structure. For example: duting the implementation of an importer for beancount I was struggling with what goes where. The example structure was really, really helpful.
• also, if you have configurations which allow different options: TELL ME THE OPTIONS! If I get an error during startup, that for config.foo the value “bar” is not allowed, I need a list of options somehwere, so many hours lost to find out what I can write to config.foo

Probably a bit more polished UX (especially for not too tech-savy people)

but I’d say the biggest difference is integrated multidevice support, either via their cloud or selfhosted…

In some Linux distributions it blocks you from installing system packages via pip, often there are then packages which can be installed via your distros package manager.

With arch for example:

sudo pacman -S python-'package'

Or, as others mentioned using venv.