git went fine...
git clone -b development https://github.com/weewx/weewx
Cloning into 'weewx'...
remote: Enumerating objects: 45, done.
remote: Counting objects: 100% (45/45), done.
remote: Compressing objects: 100% (37/37), done.
remote: Total 35534 (delta 17), reused 24 (delta 8), pack-reused 35489
Receiving objects: 100% (35534/35534), 15.58 MiB | 306.00 KiB/s, done.
Resolving deltas: 100% (27219/27219), done.
However, on my Centos7 machine running both python 2.7 and python 3.6
(python is symlinked to 3.6) I get the following...
sudo PYTHONPATH=/var/tmp/weewx4_src/weewx/bin
/var/tmp/weewx4_src/weewx/bin/wee_import --help
Traceback (most recent call last):
File "/var/tmp/weewx4_src/weewx/bin/wee_import", line 723, in <module>
import weecfg
File "/var/tmp/weewx4_src/weewx/bin/weecfg/__init__.py", line 22, in
<module>
import configobj
ModuleNotFoundError: No module named 'configobj'
sudo PYTHONPATH=/var/tmp/weewx4_src/weewx/bin
/var/tmp/weewx4_src/weewx/bin/wee_import --version
Traceback (most recent call last):
File "/var/tmp/weewx4_src/weewx/bin/wee_import", line 723, in <module>
import weecfg
File "/var/tmp/weewx4_src/weewx/bin/weecfg/__init__.py", line 22, in
<module>
import configobj
ModuleNotFoundError: No module named 'configobj'
I haven't had the time to dig, but I assume I am missing some modules in an
expected path? I still have the default weewx 3.8 installed by yum
running. Does 3.9.2 install some extra magic that I need for the 4.0b to
work?
On Tuesday, December 31, 2019 at 8:05:26 PM UTC-8, gjr80 wrote:
>
> Hi,
>
> wee_import is certainly still being worked on, this thread
> <https://groups.google.com/d/topic/weewx-user/FoiDdT-aeUA/discussion>
> refers (and there are probably others). The main chnages being the WeeWX v4
> wee_import once again supports importing from WU and it also now supports
> Weather Display imports.
>
> I had planned on having the wee_import code finished some time before
> WeeWX v4 was released, and fully intended posting some instructions for
> using the WeeWX v4 wee_import code under a WeeWX 3.x install. Though as
> the wee_import code took much longer than I thought (it has some
> significant changes to how it works in WeeWX v4) and since WeeWX v4 will be
> released RSN, I decided not to post these instructions but rather wait for
> v4 to be released. On reflection, I realise a number of folks may not
> upgrade to v4 immediately, due in part to the number of non-core WeeWX
> drivers and extensions that are yet WeeWX v4 compatible. So I have put
> together the following instructions that will allow you to use the WeeWX v4
> wee_import code under a WeeWX 3.x install (note this will have no affect
> on your WeeWX 3.x install):
>
> 1. install git if not already installed:
>
> $ sudo apt-get install git
>
> 2. create a directory for our clone and chnage to that directory:
>
> $ mkdir /var/tmp/weewx4_src
> $ cd /var/tmp/weewx4_src
>
> 3. clone the WeeWX GitHub development:
>
> $ git clone -b development https://github.com/weewx/weewx
>
> 4. check wee_import works:
>
> $ sudo PYTHONPATH=/var/tmp/weewx4_src/weewx/bin /var/tmp/weewx4_src/weewx/
> bin/wee_import --help
> $ sudo PYTHONPATH=/var/tmp/weewx4_src/weewx/bin /var/tmp/weewx4_src/weewx/
> bin/wee_import --version
>
> the version should be 0.4
>
> 5. an example import might look like:
>
> $ sudo PYTHONPATH=/var/tmp/weewx4_src/weewx/bin /var/tmp/weewx4_src/weewx/
> bin/wee_import --config=/home/weewx/weewx.conf --import-config=/var/tmp/wu
> .conf --date=2019-11-30
>
> Adjust paths to suit (you could probably leave the --config option out
> and wee_import will find the correct weewx.conf but better safe than
> sorry)
>
> You should be able to use wee_import with a suitable import config file
> and options using your existing WeeWX 3.x install setup (ie databases) but
> with the WeeWX v4 wee_import code. Note that you will need to refer to
> the v4 wee_import documentation which you will find in
> /var/tmp/weewx4_scr/weewx/docs/utilities.htm and the example import
> config files will be in /var/tmp/weewx4_src/weewx/util/import.
> Importantly, the usual caveats apply when using wee_import, ie back your
> database, do a dry run first etc but you should find importing from WU
> works provided you are using a new style long API key.
>
> Finally, you can remove the WeeWX v4 code using:
>
> $ rm -R /var/tmp/weewx4_src
>
> Gary
>
> On Wednesday, 1 January 2020 11:52:42 UTC+10, KnC Mc wrote:
>>
>> I was using wee_import with WU to generate a local webpage, and gave up
>> since May when it stopped functioning. I am not a developer at all, but
>> have been playing with HTML since v1, and hacked and thrashed my way thru
>> coding since those days for front end projects. I recently have started an
>> adventure learning python, and have figured out how to use the WU API key
>> to get some results I think I can parse. So the question...
>>
>> Is anyone still working on wee_import? Can I beta test on CentOS 7, and
>> if I can contribute I am willing to try. Weeding thru the code has been an
>> experience, but it is helping me learn. Still a total newbie with weather
>> stations and python, but this seems like a worthwhile project I am willing
>> to contribute. I am currently running a standard packaged version of
>> weewx... 3.8.0. I am not all that familiar with git, but there too, am
>> working on it. If anyone is working on wee_import, I am willing to beta
>> test and test imperial data. Haven't figured out the database piece, but I
>> have php/mysql experience that might be useful, and I am going to try and
>> apply that to my python lessons next.
>>
>> If nothing else I can stress test code (which I seem to be good at), and
>> we might be able to get wee_import in a functional state again. I don't
>> have any illusions of doing it on my own, but I am willing to help. ;)
>>
>
--
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/7b33eaae-4586-4f3c-8c62-d49e2f86449e%40googlegroups.com.
