I figured it out and fixed it in pull request 407. https://github.com/weewx/weewx/pull/407
Regards, \Leon -- Leon Shaner :: Dearborn, Michigan (iPad Pro) > On May 14, 2019, at 4:40 PM, Leon Shaner <[email protected]> wrote: > > Hi, > > I figured out that the "ImportError: No module named 'configobj'" error when > attempting to run under python3 was a missing package. > I was missing both of these: > > sudo apt-get install python3-pil > sudo apt-get install python3-configobj > > > Now the wunderfixer error when running under python3 is very similar to when > running under python2: > > $ python3 ./wunderfixer --test > Using configuration file /usr/share/weewx/weewx.conf. > Using database binding 'wx_binding', which is bound to database > 'archive_sqlite' > Traceback (most recent call last): > File "./wunderfixer", line 508, in <module> > main() > File "./wunderfixer", line 219, in main > softwaretype = "wunderfixer-%s" % __version__) > TypeError: __init__() got an unexpected keyword argument 'queue' > > > But if I comment the "queue" keyword, the error is slightly different: > > $ python3 ./wunderfixer --test > Using configuration file /usr/share/weewx/weewx.conf. > Using database binding 'wx_binding', which is bound to database > 'archive_sqlite' > Traceback (most recent call last): > File "./wunderfixer", line 508, in <module> > main() > File "./wunderfixer", line 219, in main > softwaretype = "wunderfixer-%s" % __version__) > TypeError: __init__() missing 2 required positional arguments: 'q' and > 'manager_dict' > > That's a little more helpful than the python2 error (from before): > > TypeError: __init__() takes at least 6 arguments (7 given) > > So, I guess I need to trace back "manager_dict" and "q" vs. "queue" ... > > Nobody has covered this ground already? > > Is anybody else testing first with Python2 before moving to Python3, with the > development branch? > > Regards, > \Leon > -- > Leon Shaner :: Dearborn, Michigan (iPad Pro) > >> On May 14, 2019, at 2:51 PM, Leon Shaner <[email protected]> wrote: >> >> Hey, team. =D >> >> I'm 99.9% of the way through the process of moving from the Debian release >> packages for 3.9.1 and over to the development 4.0 version. >> Before firing up weewx for the first time, I thought I'd check my >> Configuration by doing something harmless, a la: >> >> $ wunderfixer --try >> >> It throws an error and commenting the queue reference just moves the error: >> >> pi@nixie:/usr/share/weewx/bin $ ./wunderfixer --test >> Using configuration file /usr/share/weewx/weewx.conf. >> Using database binding 'wx_binding', which is bound to database >> 'archive_sqlite' >> Traceback (most recent call last): >> File "./wunderfixer", line 508, in <module> >> main() >> File "./wunderfixer", line 219, in main >> softwaretype = "wunderfixer-%s" % __version__) >> TypeError: __init__() got an unexpected keyword argument 'queue' >> >> >> And when commented: >> >> Using configuration file /usr/share/weewx/weewx.conf. >> Using database binding 'wx_binding', which is bound to database >> 'archive_sqlite' >> Traceback (most recent call last): >> File "./wunderfixer", line 508, in <module> >> main() >> File "./wunderfixer", line 219, in main >> softwaretype = "wunderfixer-%s" % __version__) >> TypeError: __init__() takes at least 6 arguments (7 given) >> >> >> I though maybe it was a python 2 vs. 3 issue, but it appears this code still >> wants python 2? >> >> pi@nixie:/usr/share/weewx/bin $ python3 ./wunderfixer --test >> Traceback (most recent call last): >> File "./wunderfixer", line 76, in <module> >> import weecfg >> File "/usr/share/weewx/bin/weecfg/__init__.py", line 22, in <module> >> import configobj >> ImportError: No module named 'configobj' >> >> Happy to file an issue for it, but first I wanted to ask if anyone has seen >> this, knows a solution, or for any other insights. >> Could it be a problem with my .conf file, or some other configuration issue? >> >> -- >> 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/3efe476b-07a6-425a-b05d-97cb401fb1d3%40googlegroups.com. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "weewx-development" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/weewx-development/vnWKrMsP1PE/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-development/A6EB07E7-F53E-4E72-9277-1A20FEB6D9CE%40isylum.org. -- 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/6F65EB14-3F1F-46D5-AF46-ED06E57EA606%40isylum.org.
