Assuming you used setup.py to install, a lot of this is covered in the documentation. For example, you’ll find the python3 packages you need to install. You’ll also see the steps to install are: python3 ./setup.py build sudo python3 ./setup.py install With the above steps, you won’t need to hand edit the scripts to use python3.
To view the WeeWX 4 setup guide in HTML, click the link below: https://htmlpreview.github.io/?https://raw.githubusercontent.com/weewx/weewx/master/docs/setup.htm > On Feb 17, 2020, at 6:02 AM, Joel Bion <[email protected]> wrote: > > > My system still has Python2 installed. I also have Python-3.8.1. Here's what > I had to do to get weewx 4.0.0b12 working on my system, which supports both > python2 and python3 simultaneously: > Since "python" on my system resolves to Python2 - I had to change the > executable scripts in /home/weewx/bin to have hashbangs that referenced > /usr/bin/python3 > I had to install PyMySQL for Python3. MySQLdb/MySQL-Python just didn't work > for me. PyMySQL worked like a charm. > I had to install Cheetah3. > I had to install Pillow for images support. The very old "imaging" package (I > think v1.1.7?) didn't work for me with Python3. > As to other Python packages needed for weewx under Python3, I haven't > checked. I had a good number installed already. The above (Cheetah3, PyMySQL, > Pillow) were the ones I had to install because I did not already have them > under Python3. > I wondered how old the stuff was in the bin/user directory - and there were a > couple of extensions I no longer used, which I just removed, and then I > upgraded my versions of __init__.py and extensions.py from the 4.0.0b12 > source tree. To get the 'purpleair' extension working in Python3, I had to > make a couple of syntax edits (print is a function, not a statement) and > (exception handling uses the 'as' keyword). When I see the 'purpleair' > extension working for a week or so, I will send these trivial edits up-stream. > The above got me running on a system supporting both Python2 and Python3. > Total work was probably about 60-90 minutes; not bad! It was nice to see how > relatively easy it was upgrading to WeeWx 4.0, and all of the changes I had > to make had nothing to do with the Weewx code. > > I'm scanning through the weewx doc to see if it references the newer Python3 > modules, but with the work-week beginning, that may not happen right away. > > At some point, when GCC 10.0 comes out, it will be time to rebuild my system > from the ground up. (I use linuxfromscratch, which is sort of a > 'build-it-yourself step-by-step distribution.) When I do that, I am going to > try to have a python3-only system under which to try to run Weewx. > > -Joel > > -- > 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/dd3aefaa-b407-4d35-808d-542acdeb3d80%40googlegroups.com. -- 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/4083AF41-00A2-48A7-91C6-4A33614BBF4C%40johnkline.com.
