subject:"Re\: \[weewx\-development\] V5.0 release candidate available"

It worked with the --config switch specified ?

If so, let me know (email is fine) and I can try to dig deeper tomorrow

On Friday, December 22, 2023 at 5:43:56 PM UTC-8 Tom Keffer wrote:

> Hmm, "weectl report run" works perfectly on my system, using Python 3.11.
>
> It's not clear from your stack trace what raised the exception. Can you 
> dig deeper?
>
> -tk
>
> On Fri, Dec 22, 2023 at 5:30 PM Vince Skahan  wrote:
>
>> I hand-edited the diff into 
>> weewx-venv/lib/python3.11/site-packages/weecfg/extension.py which worked 
>> for installing the extensions, but I get a similar message trying to run 
>> reports manually
>>
>> You might try this on a current fully patched up version to see if it 
>> works with all the updates you made after release to pypi just in case...
>>
>> (weewx-venv) vagrant@deb12:~/weewx-data$ weectl report run 
>> --config=simulator.conf
>> Using configuration file simulator.conf
>> All enabled reports will be run.
>> Generating as of last timestamp in the database.
>> Traceback (most recent call last):
>>   File "/home/vagrant/weewx-venv/bin/weectl", line 8, in 
>> sys.exit(main())
>>  ^^
>>   File "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectl.py", 
>> line 66, in main
>> namespace.func(namespace)
>>   File 
>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/__init__.py",
>>  
>> line 96, in dispatch
>> namespace.action_func(config_dict, namespace)
>>   File 
>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/report_cmd.py",
>>  
>> line 92, in run_reports
>> weectllib.report_actions.run_reports(config_dict,
>>   File 
>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/report_actions.py",
>>  
>> line 84, in run_reports
>> engine = weewx.engine.DummyEngine(config_dict)
>>  ^
>>   File 
>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weewx/engine.py", 
>> line 89, in __init__
>> self.loadServices(config_dict)
>>   File 
>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weewx/engine.py", 
>> line 157, in loadServices
>> obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>>   ^^^
>>   File 
>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weeutil/weeutil.py", 
>> line 1404, in get_object
>> module = importlib.import_module(module_name)
>>  
>>   File "/usr/lib/python3.11/importlib/__init__.py", line 126, in 
>> import_module
>> return _bootstrap._gcd_import(name[level:], package, level)
>>
>>   File "", line 1206, in _gcd_import
>>   File "", line 1178, in _find_and_load
>>   File "", line 1128, in 
>> _find_and_load_unlocked
>>   File "", line 241, in 
>> _call_with_frames_removed
>>   File "", line 1206, in _gcd_import
>>   File "", line 1178, in _find_and_load
>>   File "", line 1142, in 
>> _find_and_load_unlocked
>>
>>
>> On Friday, December 22, 2023 at 4:51:49 PM UTC-8 Tom Keffer wrote:
>>
>>> Thanks for spotting that, Vince!
>>>
>>> Fixed in commit 256cac5 
>>> 
>>> .
>>>
>>> On Fri, Dec 22, 2023 at 4:31 PM Vince Skahan  wrote:
>>>
 Tom - your xaggs extension isn't installing.  I see the identical issue 
 with one of my custom extensions too.

 (weewx-venv) vagrant@deb12:~/adds$ weectl extension install 
 --config=/home/vagrant/weewx-data/simulator.conf weewx-xaggs-master/
 Using configuration file /home/vagrant/weewx-data/simulator.conf
 Request to install 'weewx-xaggs-master/'.
 Traceback (most recent call last):
   File "/home/vagrant/weewx-venv/bin/weectl", line 8, in 
 sys.exit(main())
  ^^
   File 
 "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectl.py", line 
 66, 
 in main
 namespace.func(namespace)
   File 
 "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/__init__.py",
  
 line 96, in dispatch
 namespace.action_func(config_dict, namespace)
   File 
 "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/extension_cmd.py",
  
 line 116, in install_extension
 ext.install_extension(namespace.source)
   File 
 "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weecfg/extension.py",
  
 line 125, in install_extension
 extension_name = self.install_from_dir(extension_path)
  ^
   File 
 "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weecfg/extension.py",
  
 line 201, in install_from_dir
 save_config |= self._inject_config(installer['config'], 
 extension_name)
~^^
 KeyError: 'config'

Re: [weewx-development] V5.0 release candidate available

Hmm, "weectl report run" works perfectly on my system, using Python 3.11.

It's not clear from your stack trace what raised the exception. Can you dig
deeper?

-tk

On Fri, Dec 22, 2023 at 5:30 PM Vince Skahan  wrote:

> I hand-edited the diff into
> weewx-venv/lib/python3.11/site-packages/weecfg/extension.py which worked
> for installing the extensions, but I get a similar message trying to run
> reports manually
>
> You might try this on a current fully patched up version to see if it
> works with all the updates you made after release to pypi just in case...
>
> (weewx-venv) vagrant@deb12:~/weewx-data$ weectl report run
> --config=simulator.conf
> Using configuration file simulator.conf
> All enabled reports will be run.
> Generating as of last timestamp in the database.
> Traceback (most recent call last):
>   File "/home/vagrant/weewx-venv/bin/weectl", line 8, in 
> sys.exit(main())
>  ^^
>   File "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectl.py",
> line 66, in main
> namespace.func(namespace)
>   File
> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/__init__.py",
> line 96, in dispatch
> namespace.action_func(config_dict, namespace)
>   File
> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/report_cmd.py",
> line 92, in run_reports
> weectllib.report_actions.run_reports(config_dict,
>   File
> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/report_actions.py",
> line 84, in run_reports
> engine = weewx.engine.DummyEngine(config_dict)
>  ^
>   File
> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weewx/engine.py",
> line 89, in __init__
> self.loadServices(config_dict)
>   File
> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weewx/engine.py",
> line 157, in loadServices
> obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>   ^^^
>   File
> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weeutil/weeutil.py",
> line 1404, in get_object
> module = importlib.import_module(module_name)
>  
>   File "/usr/lib/python3.11/importlib/__init__.py", line 126, in
> import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>
>   File "", line 1206, in _gcd_import
>   File "", line 1178, in _find_and_load
>   File "", line 1128, in
> _find_and_load_unlocked
>   File "", line 241, in
> _call_with_frames_removed
>   File "", line 1206, in _gcd_import
>   File "", line 1178, in _find_and_load
>   File "", line 1142, in
> _find_and_load_unlocked
>
>
> On Friday, December 22, 2023 at 4:51:49 PM UTC-8 Tom Keffer wrote:
>
>> Thanks for spotting that, Vince!
>>
>> Fixed in commit 256cac5
>> 
>> .
>>
>> On Fri, Dec 22, 2023 at 4:31 PM Vince Skahan  wrote:
>>
>>> Tom - your xaggs extension isn't installing.  I see the identical issue
>>> with one of my custom extensions too.
>>>
>>> (weewx-venv) vagrant@deb12:~/adds$ weectl extension install
>>> --config=/home/vagrant/weewx-data/simulator.conf weewx-xaggs-master/
>>> Using configuration file /home/vagrant/weewx-data/simulator.conf
>>> Request to install 'weewx-xaggs-master/'.
>>> Traceback (most recent call last):
>>>   File "/home/vagrant/weewx-venv/bin/weectl", line 8, in 
>>> sys.exit(main())
>>>  ^^
>>>   File
>>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectl.py", line 66,
>>> in main
>>> namespace.func(namespace)
>>>   File
>>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/__init__.py",
>>> line 96, in dispatch
>>> namespace.action_func(config_dict, namespace)
>>>   File
>>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/extension_cmd.py",
>>> line 116, in install_extension
>>> ext.install_extension(namespace.source)
>>>   File
>>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weecfg/extension.py",
>>> line 125, in install_extension
>>> extension_name = self.install_from_dir(extension_path)
>>>  ^
>>>   File
>>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weecfg/extension.py",
>>> line 201, in install_from_dir
>>> save_config |= self._inject_config(installer['config'],
>>> extension_name)
>>>~^^
>>> KeyError: 'config'
>>>
>>> (weewx-venv) vagrant@deb12:~/adds$ pip3 list
>>> PackageVersion
>>> -- --
>>> certifi2023.11.17
>>> charset-normalizer 3.3.2
>>> configobj  5.0.8
>>> CT33.3.3
>>> ephem  4.1.5
>>> idna   3.6
>>> paho-mqtt  1.6.1
>>> Pillow 10.1.0
>>> pip23.0.1
>>> pyephem

Re: [weewx-development] V5.0 release candidate available

2023-12-22 Thread Greg Troxel

Tom Keffer  writes:

> Hmmm, that didn't work. If you list "wheel" as a dependency, pip isn't
> smart enough to install it first before attempting the others. So, you get
> the same error.

Is it the case that new enough pip installs it?   I just did

  $ virtualenv-3.11  FOO
  created virtual environment CPython3.11.7.final.0-64 in 451ms
creator CPython3Posix(dest=/home/gdt/FOO, clear=False, no_vcs_ignore=False, 
global=False)
seeder FromAppData(download=False, pip=bundle, setuptools=bundle, 
wheel=bundle, via=copy, app_data_dir=/home/gdt/.local/share/virtualenv)
  added seed packages: pip==23.3.1, setuptools==69.0.2, wheel==0.41.3
activators 
BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
  $ virtualenv-3.11 --version
  virtualenv 20.25.0 from 
/usr/pkg/lib/python3.11/site-packages/virtualenv/__init__.py

so it may be that people with older virtualenv are having trouble?

> I'm reluctant to create yet another step in the install process.

I'd say you aren't creating it, you are describing something that the
python world thinks is a feature!

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/rmi8r5litp9.fsf%40s1.lexort.com.

Re: [weewx-development] V5.0 release candidate available

I hand-edited the diff into 
weewx-venv/lib/python3.11/site-packages/weecfg/extension.py which worked 
for installing the extensions, but I get a similar message trying to run 
reports manually

You might try this on a current fully patched up version to see if it works 
with all the updates you made after release to pypi just in case...

(weewx-venv) vagrant@deb12:~/weewx-data$ weectl report run 
--config=simulator.conf
Using configuration file simulator.conf
All enabled reports will be run.
Generating as of last timestamp in the database.
Traceback (most recent call last):
  File "/home/vagrant/weewx-venv/bin/weectl", line 8, in 
sys.exit(main())
 ^^
  File "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectl.py", 
line 66, in main
namespace.func(namespace)
  File 
"/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/__init__.py", 
line 96, in dispatch
namespace.action_func(config_dict, namespace)
  File 
"/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/report_cmd.py",
 
line 92, in run_reports
weectllib.report_actions.run_reports(config_dict,
  File 
"/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/report_actions.py",
 
line 84, in run_reports
engine = weewx.engine.DummyEngine(config_dict)
 ^
  File 
"/home/vagrant/weewx-venv/lib/python3.11/site-packages/weewx/engine.py", 
line 89, in __init__
self.loadServices(config_dict)
  File 
"/home/vagrant/weewx-venv/lib/python3.11/site-packages/weewx/engine.py", 
line 157, in loadServices
obj = weeutil.weeutil.get_object(svc)(self, config_dict)
  ^^^
  File 
"/home/vagrant/weewx-venv/lib/python3.11/site-packages/weeutil/weeutil.py", 
line 1404, in get_object
module = importlib.import_module(module_name)
 
  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in 
import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "", line 1206, in _gcd_import
  File "", line 1178, in _find_and_load
  File "", line 1128, in 
_find_and_load_unlocked
  File "", line 241, in 
_call_with_frames_removed
  File "", line 1206, in _gcd_import
  File "", line 1178, in _find_and_load
  File "", line 1142, in 
_find_and_load_unlocked


On Friday, December 22, 2023 at 4:51:49 PM UTC-8 Tom Keffer wrote:

> Thanks for spotting that, Vince!
>
> Fixed in commit 256cac5 
> 
> .
>
> On Fri, Dec 22, 2023 at 4:31 PM Vince Skahan  wrote:
>
>> Tom - your xaggs extension isn't installing.  I see the identical issue 
>> with one of my custom extensions too.
>>
>> (weewx-venv) vagrant@deb12:~/adds$ weectl extension install 
>> --config=/home/vagrant/weewx-data/simulator.conf weewx-xaggs-master/
>> Using configuration file /home/vagrant/weewx-data/simulator.conf
>> Request to install 'weewx-xaggs-master/'.
>> Traceback (most recent call last):
>>   File "/home/vagrant/weewx-venv/bin/weectl", line 8, in 
>> sys.exit(main())
>>  ^^
>>   File "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectl.py", 
>> line 66, in main
>> namespace.func(namespace)
>>   File 
>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/__init__.py",
>>  
>> line 96, in dispatch
>> namespace.action_func(config_dict, namespace)
>>   File 
>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/extension_cmd.py",
>>  
>> line 116, in install_extension
>> ext.install_extension(namespace.source)
>>   File 
>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weecfg/extension.py", 
>> line 125, in install_extension
>> extension_name = self.install_from_dir(extension_path)
>>  ^
>>   File 
>> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weecfg/extension.py", 
>> line 201, in install_from_dir
>> save_config |= self._inject_config(installer['config'], 
>> extension_name)
>>~^^
>> KeyError: 'config'
>>
>> (weewx-venv) vagrant@deb12:~/adds$ pip3 list
>> PackageVersion
>> -- --
>> certifi2023.11.17
>> charset-normalizer 3.3.2
>> configobj  5.0.8
>> CT33.3.3
>> ephem  4.1.5
>> idna   3.6
>> paho-mqtt  1.6.1
>> Pillow 10.1.0
>> pip23.0.1
>> pyephem9.99
>> PyMySQL1.1.0
>> pyserial   3.5
>> pyusb  1.2.1
>> requests   2.31.0
>> setuptools 66.1.1
>> six1.16.0
>> urllib32.1.0
>> weewx  5.0.0rc1
>> wheel  0.42.0
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google

Re: [weewx-development] V5.0 release candidate available

Thanks for spotting that, Vince!

Fixed in commit 256cac5

.

On Fri, Dec 22, 2023 at 4:31 PM Vince Skahan  wrote:

> Tom - your xaggs extension isn't installing.  I see the identical issue
> with one of my custom extensions too.
>
> (weewx-venv) vagrant@deb12:~/adds$ weectl extension install
> --config=/home/vagrant/weewx-data/simulator.conf weewx-xaggs-master/
> Using configuration file /home/vagrant/weewx-data/simulator.conf
> Request to install 'weewx-xaggs-master/'.
> Traceback (most recent call last):
>   File "/home/vagrant/weewx-venv/bin/weectl", line 8, in 
> sys.exit(main())
>  ^^
>   File "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectl.py",
> line 66, in main
> namespace.func(namespace)
>   File
> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/__init__.py",
> line 96, in dispatch
> namespace.action_func(config_dict, namespace)
>   File
> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/extension_cmd.py",
> line 116, in install_extension
> ext.install_extension(namespace.source)
>   File
> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weecfg/extension.py",
> line 125, in install_extension
> extension_name = self.install_from_dir(extension_path)
>  ^
>   File
> "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weecfg/extension.py",
> line 201, in install_from_dir
> save_config |= self._inject_config(installer['config'], extension_name)
>~^^
> KeyError: 'config'
>
> (weewx-venv) vagrant@deb12:~/adds$ pip3 list
> PackageVersion
> -- --
> certifi2023.11.17
> charset-normalizer 3.3.2
> configobj  5.0.8
> CT33.3.3
> ephem  4.1.5
> idna   3.6
> paho-mqtt  1.6.1
> Pillow 10.1.0
> pip23.0.1
> pyephem9.99
> PyMySQL1.1.0
> pyserial   3.5
> pyusb  1.2.1
> requests   2.31.0
> setuptools 66.1.1
> six1.16.0
> urllib32.1.0
> weewx  5.0.0rc1
> wheel  0.42.0
>
>
> --
> 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 weewx-development+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-development/73f123da-7608-46d5-add0-a2b9b870d1ffn%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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/CAPq0zECTEGMYxhtD3yJJ5X00d_1ZBPWPj32%3DON3mtrmyBdXovw%40mail.gmail.com.

Re: [weewx-development] V5.0 release candidate available

Tom - your xaggs extension isn't installing.  I see the identical issue 
with one of my custom extensions too.

(weewx-venv) vagrant@deb12:~/adds$ weectl extension install 
--config=/home/vagrant/weewx-data/simulator.conf weewx-xaggs-master/
Using configuration file /home/vagrant/weewx-data/simulator.conf
Request to install 'weewx-xaggs-master/'.
Traceback (most recent call last):
  File "/home/vagrant/weewx-venv/bin/weectl", line 8, in 
sys.exit(main())
 ^^
  File "/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectl.py", 
line 66, in main
namespace.func(namespace)
  File 
"/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/__init__.py", 
line 96, in dispatch
namespace.action_func(config_dict, namespace)
  File 
"/home/vagrant/weewx-venv/lib/python3.11/site-packages/weectllib/extension_cmd.py",
 
line 116, in install_extension
ext.install_extension(namespace.source)
  File 
"/home/vagrant/weewx-venv/lib/python3.11/site-packages/weecfg/extension.py", 
line 125, in install_extension
extension_name = self.install_from_dir(extension_path)
 ^
  File 
"/home/vagrant/weewx-venv/lib/python3.11/site-packages/weecfg/extension.py", 
line 201, in install_from_dir
save_config |= self._inject_config(installer['config'], extension_name)
   ~^^
KeyError: 'config'

(weewx-venv) vagrant@deb12:~/adds$ pip3 list
PackageVersion
-- --
certifi2023.11.17
charset-normalizer 3.3.2
configobj  5.0.8
CT33.3.3
ephem  4.1.5
idna   3.6
paho-mqtt  1.6.1
Pillow 10.1.0
pip23.0.1
pyephem9.99
PyMySQL1.1.0
pyserial   3.5
pyusb  1.2.1
requests   2.31.0
setuptools 66.1.1
six1.16.0
urllib32.1.0
weewx  5.0.0rc1
wheel  0.42.0


-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/73f123da-7608-46d5-add0-a2b9b870d1ffn%40googlegroups.com.

Re: [weewx-development] V5.0 release candidate available

After a bit more investigation, it appears that some systems install
python3-wheel when they install python3-pip, some don't. Hence the
confusing results.


On Fri, Dec 22, 2023 at 2:33 PM Tom Keffer  wrote:

> Hmmm, that didn't work. If you list "wheel" as a dependency, pip isn't
> smart enough to install it first before attempting the others. So, you get
> the same error. I'm reluctant to create yet another step in the install
> process.
>
>
>
> On Fri, Dec 22, 2023 at 2:24 PM Greg  wrote:
>
>> Yes having install wheel first removes all my errors. I think it should
>> be installed by default to save any questions from people like me who don't
>> really know how this all works and what depends on what. :)
>>
>> Because I was already running the beta V5 I just renamed my venv and
>> recreated it so my weewx data would work and also if it didn't work I could
>> rename it back and all would be good. (in theory) I have installed in
>> /opt/weewx
>>
>> All looks good so far.
>>
>> https://weather.ubeaut.work/
>>
>> Thanks for the support.
>>
>>
>> On Saturday 23 December 2023 at 06:53:11 UTC+11 Vince Skahan wrote:
>>
>>> Works for me on deb12 vagrant and pi5 deb12 based raspios
>>>
>>> On Friday, December 22, 2023 at 11:42:48 AM UTC-8 Tom Keffer wrote:
>>>
 I was able to install both paho-mqtt and ephem (NB: these days, it's
 just "ephem", not "pyephem") without warnings on Debian 12 by installing
 "wheel" first:

 *python3 -m pip install wheel*
 *python3 -m pip install ephem*
 *python3 -m pip install paho-mqtt*

 Does this work for others? If so, we can put "wheel" in the
 requirements list for pip installs.

 -tk


 On Fri, Dec 22, 2023 at 11:19 AM Greg  wrote:

> Oops...I meant python version is 3.11 not pip. Pip is at the latest
> version.
> So I guess I install this way  pip 23.1 will enforce this behaviour
> change. A possible replacement is to enable the '--use-pep517'?
> I am running debian 12 by the way. Anyone else seen these messages?
>
> On Saturday 23 December 2023 at 00:09:15 UTC+11 Tom Keffer wrote:
>
>> Thanks, all! Keep them coming.
>>
>> 1. The syslog comment is annoying, but harmless. We've changed the
>> weewx unit service file to specify StandardError of journal+console. 
>> Commit
>> 940eff4
>> 
>> .
>>
>> 2. Missing Vantage records. I've noticed variants of this problem
>> when it takes a long time to download records from the console. My best 
>> is
>> that while the console is busy emitting historic records, it neglects to
>> create new ones. Hence, you miss a few records. I don't think it has
>> anything to do with V5, as the driver code hasn't changed much.
>>
>> 3. Greg, I would guess that your problems are due to using a very old
>> version of pip. You're at 3.11, but the current version is 23.3. See the
>> wiki article *Troubleshooting pip installs
>> * and see
>> if that helps.
>>
>> -tk
>>
>> On Fri, Dec 22, 2023 at 12:45 AM Greg  wrote:
>>
>>> I installed weewx using the pip method and followed the instructions.
>>> I did a pip list before installing to get the list of what other
>>> dependencies I am using.
>>>  When I installed paho-mqtt and pyephem I got these errors:
>>>
>>> Installing collected packages: paho-mqtt
>>>   DEPRECATION: paho-mqtt is being installed using the legacy
>>> 'setup.py install' method, because it does not have a 'pyproject.toml' 
>>> and
>>> the 'wheel' package is not installed. pip 23.1 will enforce this 
>>> behaviour
>>> change. A possible replacement is to enable the '--use-pep517' option.
>>> Discussion can be found at https://github.com/pypa/pip/issues/8559
>>>   Running setup.py install for paho-mqtt ... done
>>> Successfully installed paho-mqtt-1.6.1
>>>
>>> /opt/weewx$ python3 -m pip install pyephem
>>> Collecting pyephem
>>>   Using cached pyephem-9.99.tar.gz (1.4 kB)
>>>   Preparing metadata (setup.py) ... done
>>> Requirement already satisfied: ephem in
>>> ./weewx-venv/lib/python3.11/site-packages (from pyephem) (4.1.5)
>>> Installing collected packages: pyephem
>>>   DEPRECATION: pyephem is being installed using the legacy 'setup.py
>>> install' method, because it does not have a 'pyproject.toml' and the
>>> 'wheel' package is not installed. pip 23.1 will enforce this behaviour
>>> change. A possible replacement is to enable the '--use-pep517' option.
>>> Discussion can be found at https://github.com/pypa/pip/issues/8559
>>>
>>> I am currently running it in simulation mode just to see what
>>> happens.
>>> On my real system I have installed all my environment and data under

Re: [weewx-development] V5.0 release candidate available

Hmmm, that didn't work. If you list "wheel" as a dependency, pip isn't
smart enough to install it first before attempting the others. So, you get
the same error. I'm reluctant to create yet another step in the install
process.



On Fri, Dec 22, 2023 at 2:24 PM Greg  wrote:

> Yes having install wheel first removes all my errors. I think it should be
> installed by default to save any questions from people like me who don't
> really know how this all works and what depends on what. :)
>
> Because I was already running the beta V5 I just renamed my venv and
> recreated it so my weewx data would work and also if it didn't work I could
> rename it back and all would be good. (in theory) I have installed in
> /opt/weewx
>
> All looks good so far.
>
> https://weather.ubeaut.work/
>
> Thanks for the support.
>
>
> On Saturday 23 December 2023 at 06:53:11 UTC+11 Vince Skahan wrote:
>
>> Works for me on deb12 vagrant and pi5 deb12 based raspios
>>
>> On Friday, December 22, 2023 at 11:42:48 AM UTC-8 Tom Keffer wrote:
>>
>>> I was able to install both paho-mqtt and ephem (NB: these days, it's
>>> just "ephem", not "pyephem") without warnings on Debian 12 by installing
>>> "wheel" first:
>>>
>>> *python3 -m pip install wheel*
>>> *python3 -m pip install ephem*
>>> *python3 -m pip install paho-mqtt*
>>>
>>> Does this work for others? If so, we can put "wheel" in the requirements
>>> list for pip installs.
>>>
>>> -tk
>>>
>>>
>>> On Fri, Dec 22, 2023 at 11:19 AM Greg  wrote:
>>>
 Oops...I meant python version is 3.11 not pip. Pip is at the latest
 version.
 So I guess I install this way  pip 23.1 will enforce this behaviour
 change. A possible replacement is to enable the '--use-pep517'?
 I am running debian 12 by the way. Anyone else seen these messages?

 On Saturday 23 December 2023 at 00:09:15 UTC+11 Tom Keffer wrote:

> Thanks, all! Keep them coming.
>
> 1. The syslog comment is annoying, but harmless. We've changed the
> weewx unit service file to specify StandardError of journal+console. 
> Commit
> 940eff4
> 
> .
>
> 2. Missing Vantage records. I've noticed variants of this problem when
> it takes a long time to download records from the console. My best is that
> while the console is busy emitting historic records, it neglects to create
> new ones. Hence, you miss a few records. I don't think it has anything to
> do with V5, as the driver code hasn't changed much.
>
> 3. Greg, I would guess that your problems are due to using a very old
> version of pip. You're at 3.11, but the current version is 23.3. See the
> wiki article *Troubleshooting pip installs
> * and see if
> that helps.
>
> -tk
>
> On Fri, Dec 22, 2023 at 12:45 AM Greg  wrote:
>
>> I installed weewx using the pip method and followed the instructions.
>> I did a pip list before installing to get the list of what other
>> dependencies I am using.
>>  When I installed paho-mqtt and pyephem I got these errors:
>>
>> Installing collected packages: paho-mqtt
>>   DEPRECATION: paho-mqtt is being installed using the legacy
>> 'setup.py install' method, because it does not have a 'pyproject.toml' 
>> and
>> the 'wheel' package is not installed. pip 23.1 will enforce this 
>> behaviour
>> change. A possible replacement is to enable the '--use-pep517' option.
>> Discussion can be found at https://github.com/pypa/pip/issues/8559
>>   Running setup.py install for paho-mqtt ... done
>> Successfully installed paho-mqtt-1.6.1
>>
>> /opt/weewx$ python3 -m pip install pyephem
>> Collecting pyephem
>>   Using cached pyephem-9.99.tar.gz (1.4 kB)
>>   Preparing metadata (setup.py) ... done
>> Requirement already satisfied: ephem in
>> ./weewx-venv/lib/python3.11/site-packages (from pyephem) (4.1.5)
>> Installing collected packages: pyephem
>>   DEPRECATION: pyephem is being installed using the legacy 'setup.py
>> install' method, because it does not have a 'pyproject.toml' and the
>> 'wheel' package is not installed. pip 23.1 will enforce this behaviour
>> change. A possible replacement is to enable the '--use-pep517' option.
>> Discussion can be found at https://github.com/pypa/pip/issues/8559
>>
>> I am currently running it in simulation mode just to see what happens.
>> On my real system I have installed all my environment and data under
>> /opt
>> eg /opt/weewx/weewx-venv and /opt/weewx/weewx-data
>>
>> Other than that it seems to run.
>>
>> My question is should I run the install of those packages above that
>> had the error with the --use-pep517 option? I read the github
>> information that was on the link contained in the error message but it

Re: [weewx-development] V5.0 release candidate available

2023-12-22 Thread Greg

Yes having install wheel first removes all my errors. I think it should be 
installed by default to save any questions from people like me who don't 
really know how this all works and what depends on what. :)

Because I was already running the beta V5 I just renamed my venv and 
recreated it so my weewx data would work and also if it didn't work I could 
rename it back and all would be good. (in theory) I have installed in 
/opt/weewx

All looks good so far.

https://weather.ubeaut.work/

Thanks for the support.


On Saturday 23 December 2023 at 06:53:11 UTC+11 Vince Skahan wrote:

> Works for me on deb12 vagrant and pi5 deb12 based raspios
>
> On Friday, December 22, 2023 at 11:42:48 AM UTC-8 Tom Keffer wrote:
>
>> I was able to install both paho-mqtt and ephem (NB: these days, it's just 
>> "ephem", not "pyephem") without warnings on Debian 12 by installing "wheel" 
>> first:
>>
>> *python3 -m pip install wheel*
>> *python3 -m pip install ephem*
>> *python3 -m pip install paho-mqtt*
>>
>> Does this work for others? If so, we can put "wheel" in the requirements 
>> list for pip installs.
>>
>> -tk
>>
>>
>> On Fri, Dec 22, 2023 at 11:19 AM Greg  wrote:
>>
>>> Oops...I meant python version is 3.11 not pip. Pip is at the latest 
>>> version.
>>> So I guess I install this way  pip 23.1 will enforce this behaviour 
>>> change. A possible replacement is to enable the '--use-pep517'?
>>> I am running debian 12 by the way. Anyone else seen these messages?
>>>
>>> On Saturday 23 December 2023 at 00:09:15 UTC+11 Tom Keffer wrote:
>>>
 Thanks, all! Keep them coming. 

 1. The syslog comment is annoying, but harmless. We've changed the 
 weewx unit service file to specify StandardError of journal+console. 
 Commit 
 940eff4 
 
 .

 2. Missing Vantage records. I've noticed variants of this problem when 
 it takes a long time to download records from the console. My best is that 
 while the console is busy emitting historic records, it neglects to create 
 new ones. Hence, you miss a few records. I don't think it has anything to 
 do with V5, as the driver code hasn't changed much.

 3. Greg, I would guess that your problems are due to using a very old 
 version of pip. You're at 3.11, but the current version is 23.3. See the 
 wiki article *Troubleshooting pip installs 
 * and see if 
 that helps.

 -tk

 On Fri, Dec 22, 2023 at 12:45 AM Greg  wrote:

> I installed weewx using the pip method and followed the instructions.
> I did a pip list before installing to get the list of what other 
> dependencies I am using.
>  When I installed paho-mqtt and pyephem I got these errors:
>
> Installing collected packages: paho-mqtt
>   DEPRECATION: paho-mqtt is being installed using the legacy 'setup.py 
> install' method, because it does not have a 'pyproject.toml' and the 
> 'wheel' package is not installed. pip 23.1 will enforce this behaviour 
> change. A possible replacement is to enable the '--use-pep517' option. 
> Discussion can be found at https://github.com/pypa/pip/issues/8559
>   Running setup.py install for paho-mqtt ... done
> Successfully installed paho-mqtt-1.6.1
>
> /opt/weewx$ python3 -m pip install pyephem
> Collecting pyephem
>   Using cached pyephem-9.99.tar.gz (1.4 kB)
>   Preparing metadata (setup.py) ... done
> Requirement already satisfied: ephem in 
> ./weewx-venv/lib/python3.11/site-packages (from pyephem) (4.1.5)
> Installing collected packages: pyephem
>   DEPRECATION: pyephem is being installed using the legacy 'setup.py 
> install' method, because it does not have a 'pyproject.toml' and the 
> 'wheel' package is not installed. pip 23.1 will enforce this behaviour 
> change. A possible replacement is to enable the '--use-pep517' option. 
> Discussion can be found at https://github.com/pypa/pip/issues/8559
>
> I am currently running it in simulation mode just to see what happens.
> On my real system I have installed all my environment and data under 
> /opt
> eg /opt/weewx/weewx-venv and /opt/weewx/weewx-data
>
> Other than that it seems to run.
>
> My question is should I run the install of those packages above that 
> had the error with the --use-pep517 option? I read the github 
> information that was on the link contained in the error message but it 
> made 
> no sense to me.
>
> My pip version is: 3.11
>
>
> On Friday 22 December 2023 at 17:05:49 UTC+11 Hartmut Schweidler wrote:
>
>> Guten Morgen,
>>
>> Zunächst einmal vielen Dank an alle, die an der Entwicklung von weewx 
>> V5 beteiligt waren!
>>
>> Mein Installation erfolgte per "apt upgrade". auf einem

Re: [weewx-development] V5.0 release candidate available

Works for me on deb12 vagrant and pi5 deb12 based raspios

On Friday, December 22, 2023 at 11:42:48 AM UTC-8 Tom Keffer wrote:

> I was able to install both paho-mqtt and ephem (NB: these days, it's just 
> "ephem", not "pyephem") without warnings on Debian 12 by installing "wheel" 
> first:
>
> *python3 -m pip install wheel*
> *python3 -m pip install ephem*
> *python3 -m pip install paho-mqtt*
>
> Does this work for others? If so, we can put "wheel" in the requirements 
> list for pip installs.
>
> -tk
>
>
> On Fri, Dec 22, 2023 at 11:19 AM Greg  wrote:
>
>> Oops...I meant python version is 3.11 not pip. Pip is at the latest 
>> version.
>> So I guess I install this way  pip 23.1 will enforce this behaviour 
>> change. A possible replacement is to enable the '--use-pep517'?
>> I am running debian 12 by the way. Anyone else seen these messages?
>>
>> On Saturday 23 December 2023 at 00:09:15 UTC+11 Tom Keffer wrote:
>>
>>> Thanks, all! Keep them coming. 
>>>
>>> 1. The syslog comment is annoying, but harmless. We've changed the weewx 
>>> unit service file to specify StandardError of journal+console. Commit 
>>> 940eff4 
>>> 
>>> .
>>>
>>> 2. Missing Vantage records. I've noticed variants of this problem when 
>>> it takes a long time to download records from the console. My best is that 
>>> while the console is busy emitting historic records, it neglects to create 
>>> new ones. Hence, you miss a few records. I don't think it has anything to 
>>> do with V5, as the driver code hasn't changed much.
>>>
>>> 3. Greg, I would guess that your problems are due to using a very old 
>>> version of pip. You're at 3.11, but the current version is 23.3. See the 
>>> wiki article *Troubleshooting pip installs 
>>> * and see if 
>>> that helps.
>>>
>>> -tk
>>>
>>> On Fri, Dec 22, 2023 at 12:45 AM Greg  wrote:
>>>
 I installed weewx using the pip method and followed the instructions.
 I did a pip list before installing to get the list of what other 
 dependencies I am using.
  When I installed paho-mqtt and pyephem I got these errors:

 Installing collected packages: paho-mqtt
   DEPRECATION: paho-mqtt is being installed using the legacy 'setup.py 
 install' method, because it does not have a 'pyproject.toml' and the 
 'wheel' package is not installed. pip 23.1 will enforce this behaviour 
 change. A possible replacement is to enable the '--use-pep517' option. 
 Discussion can be found at https://github.com/pypa/pip/issues/8559
   Running setup.py install for paho-mqtt ... done
 Successfully installed paho-mqtt-1.6.1

 /opt/weewx$ python3 -m pip install pyephem
 Collecting pyephem
   Using cached pyephem-9.99.tar.gz (1.4 kB)
   Preparing metadata (setup.py) ... done
 Requirement already satisfied: ephem in 
 ./weewx-venv/lib/python3.11/site-packages (from pyephem) (4.1.5)
 Installing collected packages: pyephem
   DEPRECATION: pyephem is being installed using the legacy 'setup.py 
 install' method, because it does not have a 'pyproject.toml' and the 
 'wheel' package is not installed. pip 23.1 will enforce this behaviour 
 change. A possible replacement is to enable the '--use-pep517' option. 
 Discussion can be found at https://github.com/pypa/pip/issues/8559

 I am currently running it in simulation mode just to see what happens.
 On my real system I have installed all my environment and data under 
 /opt
 eg /opt/weewx/weewx-venv and /opt/weewx/weewx-data

 Other than that it seems to run.

 My question is should I run the install of those packages above that 
 had the error with the --use-pep517 option? I read the github 
 information that was on the link contained in the error message but it 
 made 
 no sense to me.

 My pip version is: 3.11

 On Friday 22 December 2023 at 17:05:49 UTC+11 Hartmut Schweidler wrote:

> Guten Morgen,
>
> Zunächst einmal vielen Dank an alle, die an der Entwicklung von weewx 
> V5 beteiligt waren!
>
> Mein Installation erfolgte per "apt upgrade". auf einem Banana Pi + 
> 1TB HDD
>
> Die folgenden Pakete werden aktualisiert (Upgrade):
>   weewx
> 1 aktualisiert, 0 neu installiert, 0 zu entfernen und 2 nicht 
> aktualisiert.
> Es müssen 2.278 kB an Archiven heruntergeladen werden.
> Nach dieser Operation werden 2.048 B Plattenplatz zusätzlich benutzt.
> Holen:1 https://weewx.com/apt-test/python3 buster/main all weewx all 
> 5.0.0rc1-1 [2.278 kB]
> Es wurden 2.278 kB in 2 s geholt (948 kB/s).
> Preconfiguring packages ...
> (Lese Datenbank ... 75361 Dateien und Verzeichnisse sind derzeit 
> installiert.)
> Vorbereitung zum Entpacken von .../weewx_5.0.0rc1-1_all.deb ...
> Entpacken von

Re: [weewx-development] V5.0 release candidate available

I was able to install both paho-mqtt and ephem (NB: these days, it's just
"ephem", not "pyephem") without warnings on Debian 12 by installing "wheel"
first:

*python3 -m pip install wheel*
*python3 -m pip install ephem*
*python3 -m pip install paho-mqtt*

Does this work for others? If so, we can put "wheel" in the requirements
list for pip installs.

-tk


On Fri, Dec 22, 2023 at 11:19 AM Greg  wrote:

> Oops...I meant python version is 3.11 not pip. Pip is at the latest
> version.
> So I guess I install this way  pip 23.1 will enforce this behaviour
> change. A possible replacement is to enable the '--use-pep517'?
> I am running debian 12 by the way. Anyone else seen these messages?
>
> On Saturday 23 December 2023 at 00:09:15 UTC+11 Tom Keffer wrote:
>
>> Thanks, all! Keep them coming.
>>
>> 1. The syslog comment is annoying, but harmless. We've changed the weewx
>> unit service file to specify StandardError of journal+console. Commit
>> 940eff4
>> 
>> .
>>
>> 2. Missing Vantage records. I've noticed variants of this problem when it
>> takes a long time to download records from the console. My best is that
>> while the console is busy emitting historic records, it neglects to create
>> new ones. Hence, you miss a few records. I don't think it has anything to
>> do with V5, as the driver code hasn't changed much.
>>
>> 3. Greg, I would guess that your problems are due to using a very old
>> version of pip. You're at 3.11, but the current version is 23.3. See the
>> wiki article *Troubleshooting pip installs
>> * and see if
>> that helps.
>>
>> -tk
>>
>> On Fri, Dec 22, 2023 at 12:45 AM Greg  wrote:
>>
>>> I installed weewx using the pip method and followed the instructions.
>>> I did a pip list before installing to get the list of what other
>>> dependencies I am using.
>>>  When I installed paho-mqtt and pyephem I got these errors:
>>>
>>> Installing collected packages: paho-mqtt
>>>   DEPRECATION: paho-mqtt is being installed using the legacy 'setup.py
>>> install' method, because it does not have a 'pyproject.toml' and the
>>> 'wheel' package is not installed. pip 23.1 will enforce this behaviour
>>> change. A possible replacement is to enable the '--use-pep517' option.
>>> Discussion can be found at https://github.com/pypa/pip/issues/8559
>>>   Running setup.py install for paho-mqtt ... done
>>> Successfully installed paho-mqtt-1.6.1
>>>
>>> /opt/weewx$ python3 -m pip install pyephem
>>> Collecting pyephem
>>>   Using cached pyephem-9.99.tar.gz (1.4 kB)
>>>   Preparing metadata (setup.py) ... done
>>> Requirement already satisfied: ephem in
>>> ./weewx-venv/lib/python3.11/site-packages (from pyephem) (4.1.5)
>>> Installing collected packages: pyephem
>>>   DEPRECATION: pyephem is being installed using the legacy 'setup.py
>>> install' method, because it does not have a 'pyproject.toml' and the
>>> 'wheel' package is not installed. pip 23.1 will enforce this behaviour
>>> change. A possible replacement is to enable the '--use-pep517' option.
>>> Discussion can be found at https://github.com/pypa/pip/issues/8559
>>>
>>> I am currently running it in simulation mode just to see what happens.
>>> On my real system I have installed all my environment and data under /opt
>>> eg /opt/weewx/weewx-venv and /opt/weewx/weewx-data
>>>
>>> Other than that it seems to run.
>>>
>>> My question is should I run the install of those packages above that had
>>> the error with the --use-pep517 option? I read the github information
>>> that was on the link contained in the error message but it made no sense to
>>> me.
>>>
>>> My pip version is: 3.11
>>>
>>>
>>> On Friday 22 December 2023 at 17:05:49 UTC+11 Hartmut Schweidler wrote:
>>>
 Guten Morgen,

 Zunächst einmal vielen Dank an alle, die an der Entwicklung von weewx
 V5 beteiligt waren!

 Mein Installation erfolgte per "apt upgrade". auf einem Banana Pi + 1TB
 HDD

 Die folgenden Pakete werden aktualisiert (Upgrade):
   weewx
 1 aktualisiert, 0 neu installiert, 0 zu entfernen und 2 nicht
 aktualisiert.
 Es müssen 2.278 kB an Archiven heruntergeladen werden.
 Nach dieser Operation werden 2.048 B Plattenplatz zusätzlich benutzt.
 Holen:1 https://weewx.com/apt-test/python3 buster/main all weewx all
 5.0.0rc1-1 [2.278 kB]
 Es wurden 2.278 kB in 2 s geholt (948 kB/s).
 Preconfiguring packages ...
 (Lese Datenbank ... 75361 Dateien und Verzeichnisse sind derzeit
 installiert.)
 Vorbereitung zum Entpacken von .../weewx_5.0.0rc1-1_all.deb ...
 Entpacken von weewx (5.0.0rc1-1) über (5.0.0b17-4) ...
 weewx (5.0.0rc1-1) wird eingerichtet ...
 Neue Version der Konfigurationsdatei /etc/weewx/skins/Ftp/skin.conf
 wird installiert ...
 Neue Version der Konfigurationsdatei /etc/weewx/skins/Mobile/skin.conf
 wird installiert ...
 Neue

Re: [weewx-development] V5.0 release candidate available

2023-12-22 Thread Greg

Oops...I meant python version is 3.11 not pip. Pip is at the latest version.
So I guess I install this way  pip 23.1 will enforce this behaviour change. 
A possible replacement is to enable the '--use-pep517'?
I am running debian 12 by the way. Anyone else seen these messages?

On Saturday 23 December 2023 at 00:09:15 UTC+11 Tom Keffer wrote:

> Thanks, all! Keep them coming. 
>
> 1. The syslog comment is annoying, but harmless. We've changed the weewx 
> unit service file to specify StandardError of journal+console. Commit 
> 940eff4 
> 
> .
>
> 2. Missing Vantage records. I've noticed variants of this problem when it 
> takes a long time to download records from the console. My best is that 
> while the console is busy emitting historic records, it neglects to create 
> new ones. Hence, you miss a few records. I don't think it has anything to 
> do with V5, as the driver code hasn't changed much.
>
> 3. Greg, I would guess that your problems are due to using a very old 
> version of pip. You're at 3.11, but the current version is 23.3. See the 
> wiki article *Troubleshooting pip installs 
> * and see if 
> that helps.
>
> -tk
>
> On Fri, Dec 22, 2023 at 12:45 AM Greg  wrote:
>
>> I installed weewx using the pip method and followed the instructions.
>> I did a pip list before installing to get the list of what other 
>> dependencies I am using.
>>  When I installed paho-mqtt and pyephem I got these errors:
>>
>> Installing collected packages: paho-mqtt
>>   DEPRECATION: paho-mqtt is being installed using the legacy 'setup.py 
>> install' method, because it does not have a 'pyproject.toml' and the 
>> 'wheel' package is not installed. pip 23.1 will enforce this behaviour 
>> change. A possible replacement is to enable the '--use-pep517' option. 
>> Discussion can be found at https://github.com/pypa/pip/issues/8559
>>   Running setup.py install for paho-mqtt ... done
>> Successfully installed paho-mqtt-1.6.1
>>
>> /opt/weewx$ python3 -m pip install pyephem
>> Collecting pyephem
>>   Using cached pyephem-9.99.tar.gz (1.4 kB)
>>   Preparing metadata (setup.py) ... done
>> Requirement already satisfied: ephem in 
>> ./weewx-venv/lib/python3.11/site-packages (from pyephem) (4.1.5)
>> Installing collected packages: pyephem
>>   DEPRECATION: pyephem is being installed using the legacy 'setup.py 
>> install' method, because it does not have a 'pyproject.toml' and the 
>> 'wheel' package is not installed. pip 23.1 will enforce this behaviour 
>> change. A possible replacement is to enable the '--use-pep517' option. 
>> Discussion can be found at https://github.com/pypa/pip/issues/8559
>>
>> I am currently running it in simulation mode just to see what happens.
>> On my real system I have installed all my environment and data under /opt
>> eg /opt/weewx/weewx-venv and /opt/weewx/weewx-data
>>
>> Other than that it seems to run.
>>
>> My question is should I run the install of those packages above that had 
>> the error with the --use-pep517 option? I read the github information 
>> that was on the link contained in the error message but it made no sense to 
>> me.
>>
>> My pip version is: 3.11
>>
>>
>> On Friday 22 December 2023 at 17:05:49 UTC+11 Hartmut Schweidler wrote:
>>
>>> Guten Morgen,
>>>
>>> Zunächst einmal vielen Dank an alle, die an der Entwicklung von weewx V5 
>>> beteiligt waren!
>>>
>>> Mein Installation erfolgte per "apt upgrade". auf einem Banana Pi + 1TB 
>>> HDD
>>>
>>> Die folgenden Pakete werden aktualisiert (Upgrade):
>>>   weewx
>>> 1 aktualisiert, 0 neu installiert, 0 zu entfernen und 2 nicht 
>>> aktualisiert.
>>> Es müssen 2.278 kB an Archiven heruntergeladen werden.
>>> Nach dieser Operation werden 2.048 B Plattenplatz zusätzlich benutzt.
>>> Holen:1 https://weewx.com/apt-test/python3 buster/main all weewx all 
>>> 5.0.0rc1-1 [2.278 kB]
>>> Es wurden 2.278 kB in 2 s geholt (948 kB/s).
>>> Preconfiguring packages ...
>>> (Lese Datenbank ... 75361 Dateien und Verzeichnisse sind derzeit 
>>> installiert.)
>>> Vorbereitung zum Entpacken von .../weewx_5.0.0rc1-1_all.deb ...
>>> Entpacken von weewx (5.0.0rc1-1) über (5.0.0b17-4) ...
>>> weewx (5.0.0rc1-1) wird eingerichtet ...
>>> Neue Version der Konfigurationsdatei /etc/weewx/skins/Ftp/skin.conf wird 
>>> installiert ...
>>> Neue Version der Konfigurationsdatei /etc/weewx/skins/Mobile/skin.conf 
>>> wird installiert ...
>>> Neue Version der Konfigurationsdatei /etc/weewx/skins/Rsync/skin.conf 
>>> wird installiert ...
>>>
>>> Konfigurationsdatei »/etc/weewx/skins/Seasons/skin.conf«
>>>  ==> Geändert (von Ihnen oder von einem Skript) seit der Installation.
>>>  ==> Paketverteiler hat eine aktualisierte Version herausgegeben.
>>>Wie möchten Sie vorgehen? Ihre Wahlmöglichkeiten sind:
>>> Y oder I : Die Version des Paket-Betreuers installieren
>>> N oder O : Die momentan installierte Version

Re: [weewx-development] V5.0 release candidate available

2023-12-22 Thread Claudio

does it work on Raspberry 5 and Debian version: 12 (bookworm)?
Claudio
Il giorno venerdì 22 dicembre 2023 alle 19:12:47 UTC+1 Vince Skahan ha 
scritto:

> I set up a couple instances via weewx-multi following 
> https://github.com/weewx/weewx/wiki/weewx-multi and it looks like the 
> generated weewx@.service file needs a little tweak.
>
> My pip installation generated a weewx@.service file that had ExecStart 
> pointing to weewx.conf, but it should point to %i.conf so the instance name 
> is used.  After making that change multi works just amazingly well.  So 
> easy.
>
>

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/29bf6a31-9771-45df-9eec-6a7c448c9b8fn%40googlegroups.com.

Re: [weewx-development] V5.0 release candidate available

I set up a couple instances via weewx-multi 
following https://github.com/weewx/weewx/wiki/weewx-multi and it looks like 
the generated weewx@.service file needs a little tweak.

My pip installation generated a weewx@.service file that had ExecStart 
pointing to weewx.conf, but it should point to %i.conf so the instance name 
is used.  After making that change multi works just amazingly well.  So 
easy.

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/70ff0050-abcb-4b2c-b93c-135fa69ee418n%40googlegroups.com.

Re: [weewx-development] V5.0 release candidate available

On Friday, December 22, 2023 at 5:09:15 AM UTC-8 Tom Keffer wrote:

3. Greg, I would guess that your problems are due to using a very old
version of pip. You're at 3.11, but the current version is 23.3. See the
wiki article *Troubleshooting pip installs
* and see if that
helps.

On Fri, Dec 22, 2023 at 12:45 AM Greg wrote:

I installed weewx using the pip method and followed the instructions.
I did a pip list before installing to get the list of what other
dependencies I am using.
When I installed paho-mqtt and pyephem I got these errors:

Installing collected packages: paho-mqtt
DEPRECATION: paho-mqtt is being installed using the legacy 'setup.py
install' method, because it does not have a 'pyproject.toml' and the
'wheel' package is not installed. pip 23.1 will enforce this behaviour
change. A possible replacement is to enable the '--use-pep517' option.
Discussion can be found at https://github.com/pypa/pip/issues/8559
Running setup.py install for paho-mqtt ... done
Successfully installed paho-mqtt-1.6.1

My question is should I run the install of those packages above that had
the error with the --use-pep517 option? I read the github information that
was on the link contained in the error message but it made no sense to me.

I see these too on debian12 with pip 23.0.1 for those two packages...

- paho-mqtt has an open issue on this but they seem to be thrashing
among the devs a bit working it
- https://github.com/eclipse/paho.mqtt.python/issues/706
- I couldn't find an issue on pyephem's github so I opened one there
- https://github.com/brandon-rhodes/pyephem/issues/268

The warnings do go away if you add the switch ala:

(weewx-venv) vagrant@deb12:~$ pip install --use-pep517 paho-mqtt
Collecting paho-mqtt
Using cached paho-mqtt-1.6.1.tar.gz (99 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: paho-mqtt
Building wheel for paho-mqtt (pyproject.toml) ... done
Created wheel for paho-mqtt: filename=paho_mqtt-1.6.1-py3-none-any.whl
size=62120
sha256=f329e400c6f3932151a07b46b5f098cd025392b454e94d874d48d7cc6f2c2d91
Stored in directory:
/home/vagrant/.cache/pip/wheels/29/ea/a5/ba9a63aaf4cd4e16e8a87ee31fb4d11b04ff5e1735d312619a
Successfully built paho-mqtt
Installing collected packages: paho-mqtt
Successfully installed paho-mqtt-1.6.1

Re: [weewx-development] V5.0 release candidate available

Can confirm that worked,
Thanks,
Ian

On Friday, December 22, 2023 at 4:27:17 PM UTC Steeple Ian wrote:

> Thanks Matthew, I have a fork of gw1000 so I can do it directly from there.
>
> Ian
>
> On Friday, December 22, 2023 at 4:20:36 PM UTC matthew wall wrote:
>
>> I guess the second last line is the key one. Being trying to dig my way 
>> out of this one without success. I never had a problem with any of the 
>> other recent builds of version 5.
>>
>> Any help would be appreciated,
>>
>>
>> hi ian,
>>
>> we just discovered this as well.  the 'StrictVersion' parser does not 
>> handle 'rc' correctly.  here are some details:
>>
>>  https://peps.python.org/pep-0386/
>>
>> as a workaround, you can extract the gw1000 tarball/zip, modify the 
>> install.py, then use 'weectl extension' to load from the directory instead 
>> of directly from the url.
>>
>> in install.py, replace the StrictVersion conditional at line 382 with a 
>> simple "if False:"
>>
>> m
>>
>>

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/e8df6e2c-6f80-4419-8029-9c95bb528a8en%40googlegroups.com.

Re: [weewx-development] V5.0 release candidate available

Quick question Matthew, did you mean replace the whole line?

On Friday, December 22, 2023 at 4:27:17 PM UTC Steeple Ian wrote:

> Thanks Matthew, I have a fork of gw1000 so I can do it directly from there.
>
> Ian
>
> On Friday, December 22, 2023 at 4:20:36 PM UTC matthew wall wrote:
>
>> I guess the second last line is the key one. Being trying to dig my way 
>> out of this one without success. I never had a problem with any of the 
>> other recent builds of version 5.
>>
>> Any help would be appreciated,
>>
>>
>> hi ian,
>>
>> we just discovered this as well.  the 'StrictVersion' parser does not 
>> handle 'rc' correctly.  here are some details:
>>
>>  https://peps.python.org/pep-0386/
>>
>> as a workaround, you can extract the gw1000 tarball/zip, modify the 
>> install.py, then use 'weectl extension' to load from the directory instead 
>> of directly from the url.
>>
>> in install.py, replace the StrictVersion conditional at line 382 with a 
>> simple "if False:"
>>
>> m
>>
>>

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/8aee4c4a-389e-40c1-a453-68d14b4d8c2an%40googlegroups.com.

Re: [weewx-development] V5.0 release candidate available

Thanks Matthew, I have a fork of gw1000 so I can do it directly from there.

Ian

On Friday, December 22, 2023 at 4:20:36 PM UTC matthew wall wrote:

> I guess the second last line is the key one. Being trying to dig my way 
> out of this one without success. I never had a problem with any of the 
> other recent builds of version 5.
>
> Any help would be appreciated,
>
>
> hi ian,
>
> we just discovered this as well.  the 'StrictVersion' parser does not 
> handle 'rc' correctly.  here are some details:
>
>  https://peps.python.org/pep-0386/
>
> as a workaround, you can extract the gw1000 tarball/zip, modify the 
> install.py, then use 'weectl extension' to load from the directory instead 
> of directly from the url.
>
> in install.py, replace the StrictVersion conditional at line 382 with a 
> simple "if False:"
>
> m
>
>

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/9f9e18b0-8fc6-4f68-850d-4745996915dbn%40googlegroups.com.

Re: [weewx-development] V5.0 release candidate available

2023-12-22 Thread matthew wall



I guess the second last line is the key one. Being trying to dig my way out 
of this one without success. I never had a problem with any of the other 
recent builds of version 5.

Any help would be appreciated,


hi ian,

we just discovered this as well.  the 'StrictVersion' parser does not 
handle 'rc' correctly.  here are some details:

 https://peps.python.org/pep-0386/

as a workaround, you can extract the gw1000 tarball/zip, modify the 
install.py, then use 'weectl extension' to load from the directory instead 
of directly from the url.

in install.py, replace the StrictVersion conditional at line 382 with a 
simple "if False:"

m

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/9097586a-506e-4421-ac46-254d6d2139b2n%40googlegroups.com.

Re: [weewx-development] V5.0 release candidate available

Installed the release candidate using pip. All working fine using simulator 
driver. Then tried to install Gary's weewx-gw1000.py driver and repeatedly 
get this error: -

(weewx-venv) Ian@bookworm:~$ weectl extension install 
https://github.com/gjr80/weewx-gw1000/releases/download/v0.6.0b2/gw1000-0.6.0b2.tar.gz
Using configuration file /home/Ian/weewx-data/weewx.conf
Request to install 
'https://github.com/gjr80/weewx-gw1000/releases/download/v0.6.0b2/gw1000-0.6.0b2.tar.gz'.
Extracting from tar archive /tmp/tmpdoa3q052
Traceback (most recent call last):
  File "/home/Ian/weewx-venv/bin/weectl", line 8, in 
sys.exit(main())
 ^^
  File "/home/Ian/weewx-venv/lib/python3.11/site-packages/weectl.py", line 
66, in main
namespace.func(namespace)
  File 
"/home/Ian/weewx-venv/lib/python3.11/site-packages/weectllib/__init__.py", 
line 96, in dispatch
namespace.action_func(config_dict, namespace)
  File 
"/home/Ian/weewx-venv/lib/python3.11/site-packages/weectllib/extension_cmd.py", 
line 116, in install_extension
ext.install_extension(namespace.source)
  File 
"/home/Ian/weewx-venv/lib/python3.11/site-packages/weecfg/extension.py", 
line 114, in install_extension
extension_name = self._install_from_file(test_fd.name, 
info.get_content_subtype())

 ^
  File 
"/home/Ian/weewx-venv/lib/python3.11/site-packages/weecfg/extension.py", 
line 154, in _install_from_file
extension_name = self.install_from_dir(extension_dir)

  File 
"/home/Ian/weewx-venv/lib/python3.11/site-packages/weecfg/extension.py", 
line 165, in install_from_dir
installer_path, installer = 
weecfg.get_extension_installer(extension_dir)

^
  File 
"/home/Ian/weewx-venv/lib/python3.11/site-packages/weecfg/__init__.py", 
line 738, in get_extension_installer
installer = loader()

  File "/tmp/tmpekv6izgc/gw1000/install.py", line 377, in loader
  File "/tmp/tmpekv6izgc/gw1000/install.py", line 382, in __init__
  File 
"/home/Ian/weewx-venv/lib/python3.11/site-packages/setuptools/_distutils/version.py",

line 54, in __init__
self.parse(vstring)
  File 
"/home/Ian/weewx-venv/lib/python3.11/site-packages/setuptools/_distutils/version.py",

line 157, in parse
raise ValueError("invalid version number '%s'" % vstring)
ValueError: invalid version number '5.0.0rc1'
(weewx-venv) Ian@bookworm:~$ 

I guess the second last line is the key one. Being trying to dig my way out 
of this one without success. I never had a problem with any of the other 
recent builds of version 5.

Any help would be appreciated,

Thanks,
Ian

On Friday, December 22, 2023 at 1:38:26 PM UTC matthew wall wrote:

> On Friday, December 22, 2023 at 8:31:47 AM UTC-5 Paul R Anderson wrote:
>
> On startup __init__.py now logs this:
> Dec 21 06:47:19 hall-9000 weewxd[4484]: INFO weewx: Adding 'user' 
> directory '/home/panders/weewx-data/bin'
>
> First time I saw it I thought wait that directory should exist, it's where 
> my extensions live, hope they're OK. Then I realized it's just adding the 
> dir to PYTHONPATH
>
>  
> addressed in commit 
> https://github.com/weewx/weewx/commit/e402cd4dee6fb9db397b224c4c05188b884c8d69
> 
>

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/18cc73e5-f691-4dd4-8043-b96e1c2d141fn%40googlegroups.com.

Re: [weewx-development] V5.0 release candidate available

2023-12-22 Thread matthew wall

On Friday, December 22, 2023 at 8:31:47 AM UTC-5 Paul R Anderson wrote:

On startup __init__.py now logs this:
Dec 21 06:47:19 hall-9000 weewxd[4484]: INFO weewx: Adding 'user' directory 
'/home/panders/weewx-data/bin'

First time I saw it I thought wait that directory should exist, it's where 
my extensions live, hope they're OK. Then I realized it's just adding the 
dir to PYTHONPATH

 
addressed in commit https://github.com/weewx/weewx/commit/e402cd4dee6fb9db397b224c4c05188b884c8d69

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/8c48442b-5a13-44c8-bb54-67bd9de04509n%40googlegroups.com.

Re: [weewx-development] V5.0 release candidate available

2023-12-22 Thread Paul R Anderson

Extremely nitpicky, this could be just me :)
On startup __init__.py now logs this:
Dec 21 06:47:19 hall-9000 weewxd[4484]: INFO weewx: Adding 'user' directory
'/home/panders/weewx-data/bin'

First time I saw it I thought wait that directory should exist, it's where
my extensions live, hope they're OK. Then I realized it's just adding the
dir to PYTHONPATH
Perhaps change  __init__.py logging line to slightly more descriptive
log.info("Adding 'user' directory '%s' to PYTHONPATH" % lib_dir)
So it produces:
Dec 22 07:52:36 hall-9000 weewxd[508]: INFO weewx: Adding 'user' directory
'/home/panders/weewx-data/bin' to PYTHONPATH
Paul

On Thu, Dec 21, 2023 at 6:07 PM Tom Keffer  wrote:

> Celebrate the solstice (coming up in 4 hours) and the start of Winter with
> a WeeWX release candidate!
>
> *Changes since b17*
> We gave up on a standalone logger and have gone back to whatever your
> system uses. This is more robust to permission problems, but may make it
> harder to get the logs back out. See the wiki article *View logs
> * for tips on how to
> convince your system to let you have a look.
>
> As always, you can add a [Logging] section to weewx.conf and set up your
> own rotating log system. See the article *WeeWX V4 and logging
> * for how to do
> this.
>
> *Pip*
>
> For pip installs, please delete your old virtual environment, then install
> from scratch by following the pip install instructions
> .
> While upgrading should work, we are particularly interested in the
> experience of a new install, including setting up a daemon and udev files.
> Make sure to follow the new instructions that use a daemon setup script.
>
>
> *Debian*
>
> For Debian package installs, modify /etc/apt/sources.list as follows:
>
> *echo "deb [arch=all] https://weewx.com/apt-test/python3 
>  buster main" | sudo tee 
> /etc/apt/sources.list.d/weewx.list*
>
> Note the "apt-test". This tells apt to look there for the beta release,
> instead of the normal repository. You may want to change it back when
> you're done.
>
>
> *Red Hat*
>
> For Red Hat package installs, put this in /etc/yum.repos.d/weewx.repo
>
> *[weewx]
> name=weewx
> baseurl=http://weewx.com/yum-test/weewx/el9 
> 
> enabled=1*
>
> Note the "yum-test". This tells yum to look there for the beta release,
> instead of the normal repository. Again, you may want to change things back
> when you're done.
>
>
> *What we're looking for*
>
> 1. We are interested in your upgrade experience. Did the installers get
> your configuration file right? Skins? Is the daemon configured correctly?
>
> 2. With this release, we have included udev rules to set the correct
> permissions for devices. Did it work? If not, did unplugging then
> replugging the device work?
>
> 3. How about logging? Is it going to your system logger? Do the labels
> look reasonable?
>
> *Thanks!*
>
> -Tom & Matt
>
> --
> 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 weewx-development+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-development/CAPq0zECFSEWf9immM3fFroWU79GcYyT65ibe8w1hWd-XJ92s1g%40mail.gmail.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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/CAOAVAeebKnQcGoori18Lokk5jwRutNvH_wbKx4wskvX-u62wSw%40mail.gmail.com.

Re: [weewx-development] V5.0 release candidate available