The problem is not using an Almanac object but rather instantiating one. The Almanac signature has changed and backwards compatibility has not been retained. Existing code that instantiates an Almanac object with explicitly set moon_phases, eg
my_almanac = Almanac(time_ts=ts, lat=lat, lon=lon, moon_phases=my_moon_phases) now throws an error because the moon_phases parameter no longer exists in the Almanac signature. On Saturday, 28 February 2026 at 03:46:58 UTC+10 Karen K wrote: R schrieb am Donnerstag, 26. Februar 2026 um 00:42:59 UTC+1: I note the class Almanac signature has changed in v5.3.0 with the removal of the moon_phases parameter. Understand that moon phases are still supported through the texts parameter; however, any existing user code that calls almanac.Almanac with a moon_phases argument will fail. Guess this will at least be covered in the upgrade guide? The change log does not mention the change. No. You can still write something like $almanac(moon_phases=[...]).moon_phase. It will work as before. -- 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 visit https://groups.google.com/d/msgid/weewx-user/f5988c34-b486-4c5e-866b-73a0f4c82912n%40googlegroups.com.
