I prefer the old behavior on shutdown. A normal exit status shouldn't prompt a trace. That's why the debug option exists. It's the same reason I don't generally want to see Linux core dumps. I can't fix the kernel. But I have the option to turn it off or on. It makes systemctl status weewx have nice output. I don't want to have the patch the source myself. Hence the suggested change. A better solution might be an config file option traceback_on_exit = NO|yes or YES|no.
I switched from using my preferred FreeBSD OS to using Raspbian due to the changes in logging. Irritated that not all the extensions followed the same feature upgrade. The change to logging made sense. I am not python savvy enough to provide patches to make FreeBSD work with V4, it wasn't a mainstream support O/S for weewx. I tracked the V4 BETA stuff for a while, but again realized, I don't want to know how the application works enough to patch I just want to use it. As a user, many of whom don't like change, I prefer the old way, the 'expected' way an application closes in a normal fashion. With suggestions for providing the 'old' way if that way was easy to implement. I figured I'd cast my vote otherwise no one would know. Now, I have to patch the source on each upgrade to restore the old behavior. -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/bd6d1c48-2918-4b9d-b52c-7ef186038cf3%40googlegroups.com.
