Lost pyephem after upgrade to 5.1 and/or Bookworm

[Chris Alemany]

Hi all,

I'm running weewx on a Debian system. Last week I updated to Bookworm and weewx 5.1 and it appears to have broken pyephem.  

I am using the pip method and pyephem is reported as installed successfully in the weewx-venv folders (and I can confirm there are folders for both 3.9 and 3.11 that both have pyephem modules inside.

I've also installed with apt install python3-ephem on the system as a whole.

Regardless, weewx is reporting: 'pyephem' not detected in the logs.

I've seen a few other people mention this when upgrading here but having seen any firm resolutions?  I've tried running the weewx installer again, I actually ran the whole pip install procedure up to python3 -m pip install weewx. It reports everything is installed, but upon launch, weewx doesn't see pyephem.

Is there another log I can find to see if there are failures with linking to pyephem?

Thanks for any suggestions

Chris

[Tom Keffer]

Things to check/try:

1. Make sure the instance of python you think you are running is the same as the version for which ephem was installed.

2. If you did apt install python3-ephem, but try to run out of a virtual environment, the Python interpreter won't find it.

3. If you are doing a pip install, use 

   python3 -m pip list -v

to see what is installed for that particular instance of Python

4. You didn't say if this is happening all the time, or just when running as a daemon, but if you're doing the latter, make sure you use the instance of Python for which pyephem is installed. For a pip install, that means you need the explicit path to the instance of Python inside the virtual environment.

-tk

--
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 weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/3e13dbd6-0bcc-4e23-9a9d-42b9797b85d0n%40googlegroups.com.

[Chris Alemany]

Thanks Tom,

I was very much down that road.  It looks like there were more than a couple modules that were not brought over when I upgraded the system from Debian 11 to 12/bookworm and/or when I went from weewx 5.0 to 5.1.  There was more than one version of perl (3.9 and 3.11) in the lib directories so that gave me the thought to redo the weewx-venv.

Regardless, after removing the venv`folder and backing up the weewx-data folder, I went back through the pip setup/install process, it successfully got all of the modules plus others needed for other extensions, and now I am back up and running after copying back over my archive, weewx.conf, skins, bin/user and public_html from backup.

All is good!

Sometimes this process of asking is just a good way to spur myself to doing.

Hopefully this helps someone else.

[Tom Keffer]

The beauty of the virtual environment is that you can completely blow it away without touching anything else. Just a simple "rm -r ~/weewx-venv", then start again. No need to mess with archives, skins, etc.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/4a50aa4f-9558-48d9-9202-4cf4bd979e52n%40googlegroups.com.

[Christopher Joseph Alemany]

Yes! It is very very nice to troubleshoot! I should also mention I dropped and rebuilt the daily summaries as well just to be safe.

“They always tell me it takes time. How much more time do you want...for your progress?”

James Baldwin

Chris Alemany

3854 6th Ave

Port Alberni, BC

V9Y4M2

h:250-723-0889

w: 250-753-3245 x2106

e: chri...@gmail.com

w: www.chrisalemany.ca

w: www.alberniweather.ca

w: www.vifreightbyrail.ca

On Oct 17, 2024, at 14:39, Tom Keffer <tke...@gmail.com> wrote:



To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEB7n-fAZhUi%2BcaGi9T%3DHnsExpa3BzxMxN_XN5ZaFyu-CQ%40mail.gmail.com.