FWIW, it's more work but a generally better way to approach essentially forking things in core weewx is to create your own skin based on some starting point, disable the skin that comes with weewx, and enable your custom skin that has a different name. Bonus points if you make your custom skin installable with wee_extension.
That keeps you safe from your modifications being altered by a future weewx update, as weewx won't stomp on things that didn't come with weewx. -- You received this message because you are subscribed to the Google Groups "weewx-user" 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-user/6688787a-3b2a-4864-b807-377bf97a3c16n%40googlegroups.com.
