OK, I see why I missed it, the actual commit that made the change was dated quite some time ago, 21 November 2017 (v3.8.0 vintage), but it appears it did not make a release until 3.9.0 for some reason - perhaps it is my limited appreciation on the finer points of git or maybe there was a disturbance in the git Force. The accumulators have worked quite happily previously accepting longs so the check in accum.py could be changed to accept longs, but that is python 2 specific and Tom is slowly moving the code base to be python 3 compatible (Python 3 does away with longs, everything is an int). So the good news is when a python 3 version of WeeWX is released cmon 0.16 will work just fine :). In the meantime I guess the cmon change needs to stay.
Mystery solved. Gary On Monday, 18 February 2019 11:47:47 UTC+10, Luc Heijst wrote: > > Hi Gary, > > Accum v.3.9 throws an exception if the parameter is not a float or an int > where accum v.3.8.2 didn’t. > So I believe the long parameter of cmon itself is not the problem because > it didn’t cause any exceptions before. > > Luc > -- 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]. For more options, visit https://groups.google.com/d/optout.
