On Sunday, May 10, 2020 at 1:27:01 PM UTC-7, Vince Skahan wrote: > > > - (2) stop using the os's python modules. Bundle at least the add-on > modules weewx needs 'with' weewx core, located under the weewx tree > someplace. Fix up PYTHONPATH or the like as needed. > > Just wanted to add one thought and a question for Tom/Matthew before I spend any time fiddling.
At $work we bundle 'all' our OSS software into a separate big-honkin' /opt tree and 'never' install any perl/python variants or modules/libraries to any directory owned by the operating system. In short, we tell people to use 'our' hand-built perl and python, and we install any modules/libraries they need to under that tree. So if hypothetically we put all of weewx under /home/weewx still...... - /home/weewx/bin would contain things executable - /home/weewx/etc would contain config files - /home/weewx/var would contain things more read/write - weewx's python3 would be /home/weewx/bin/python3 - weewx's pip3 would be /home/weewx/bin/pip3 - and you would always use weewx's pip3 when you wanted to install modules using pip Basically all you'd need to do is compile your own python ala "configure --prefix=/home/weewx/python" or something like that.... Or have two packages ? One with weewx, one with weewx-python ? -- 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/edf62268-4126-47f8-a96e-e6f948f0f55b%40googlegroups.com.
