I just finished a new install on a new machine.
b10 works fine with Python 2.7.17 and default skin.
On Friday, January 24, 2020 at 6:34:14 PM UTC-5, Thomas Keffer wrote:
>
> Could you all do a pull and give it another try? The flow path between
> byte strings and unicode are more controlled now,
On Friday, January 24, 2020 at 5:34:14 PM UTC-6, Thomas Keffer wrote:
>
> Could you all do a pull and give it another try? The flow path between
> byte strings and unicode are more controlled now, making the results less
> prone to decode errors.
>
> At least, that's the theory!
>
> -tk
>
My w
Fine for me under both python2 and 3.
Gary
On Saturday, 25 January 2020 09:34:14 UTC+10, Thomas Keffer wrote:
>
> Could you all do a pull and give it another try? The flow path between
> byte strings and unicode are more controlled now, making the results less
> prone to decode errors.
>
> At l
Could you all do a pull and give it another try? The flow path between byte
strings and unicode are more controlled now, making the results less prone
to decode errors.
At least, that's the theory!
-tk
On Thu, Jan 23, 2020 at 8:48 PM P Simmons wrote:
>
> Updated to db1b41e, problem solved.
>
>
Updated to db1b41e, problem solved.
Thanks!
Paul
--
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+unsubscr...@googlegroups.com.
To view this discussio
Just installed version 4 on my PI 4, and hit this error. Came to google
groups and you'd already fixed it. Awesome.
On Thursday, January 23, 2020 at 5:16:52 PM UTC-8, Thomas Keffer wrote:
>
> Rats. Try this version.
>
> On Thu, Jan 23, 2020 at 5:07 PM Thomas Keffer > wrote:
>
>> Try replacing yo
Awesome. Just got version 4 installed, hit this same error, and found the
solution in short order.
Thanks!
On Thursday, January 23, 2020 at 5:30:41 PM UTC-8, gjr80 wrote:
>
> Ha, first version worked fine! Second version was fine too. Checked under
> both python 2 and 3.
>
> Gary
>
> On Friday,
Ha, first version worked fine! Second version was fine too. Checked under
both python 2 and 3.
Gary
On Friday, 24 January 2020 11:16:52 UTC+10, Thomas Keffer wrote:
>
> Rats. Try this version.
>
> On Thu, Jan 23, 2020 at 5:07 PM Thomas Keffer > wrote:
>
>> Try replacing your version of weewx/de
Rats. Try this version.
On Thu, Jan 23, 2020 at 5:07 PM Thomas Keffer wrote:
> Try replacing your version of weewx/defaults.py with the attached and
> see if that helps.
>
> Bit of a hack. I'll keep searching for something more elegant.
>
> On Thu, Jan 23, 2020 at 3:54 PM Thomas Keffer wrote:
>
Try replacing your version of weewx/defaults.py with the attached and
see if that helps.
Bit of a hack. I'll keep searching for something more elegant.
On Thu, Jan 23, 2020 at 3:54 PM Thomas Keffer wrote:
> Just as I suspected. The patch that fixed things for configobj v4.7.2,
> broke v5.0.6.
>
Just as I suspected. The patch that fixed things for configobj v4.7.2,
broke v5.0.6.
Can't help but feel that I'm approaching this all wrong. Got to give it a
deep think.
-tk
On Thu, Jan 23, 2020 at 3:38 PM gjr80 wrote:
> 5.0.6
>
> gary@stretch40:~/src/weewx$ python2 -c "import configobj;
> pr
5.0.6
gary@stretch40:~/src/weewx$ python2 -c "import configobj;
print(configobj.__version__)"
5.0.6
Gary
On Friday, 24 January 2020 09:37:04 UTC+10, Thomas Keffer wrote:
>
> OK, now we know what went wrong, but we don't know why.
>
> What version of ConfigObj are you using?
>
> *python2 -c "imp
OK, now we know what went wrong, but we don't know why.
What version of ConfigObj are you using?
*python2 -c "import configobj; print(configobj.__version__)"*
-tk
On Thu, Jan 23, 2020 at 3:22 PM gjr80 wrote:
> That got it!
>
> Gary
>
> Jan 24 09:10:51 stretch40 weewx[777] INFO weewx.engine:
That got it!
Gary
Jan 24 09:10:51 stretch40 weewx[777] INFO weewx.engine: Starting main
packet loop.
Jan 24 09:15:16 stretch40 weewx[777] INFO weewx.manager: Added record 2020-
01-24 09:15:00 AEST (1579821300) to database 'weewx.sdb'
Jan 24 09:15:16 stretch40 weewx[777] INFO weewx.manager: Added
Grumble!
Try this one.
On Wed, Jan 22, 2020 at 7:16 PM gjr80 wrote:
> Hmm, looks like the extra log line is itself producing an error:
>
> Jan 23 13:10:14 stretch40 weewx[1174] INFO weewx.manager: Added record
> 2020-01-23 13:10:00 AEST (1579749000) to database 'weewx.sdb'
> Jan 23 13:10:14 s
Hmm, looks like the extra log line is itself producing an error:
Jan 23 13:10:14 stretch40 weewx[1174] INFO weewx.manager: Added record 2020-
01-23 13:10:00 AEST (1579749000) to database 'weewx.sdb'
Jan 23 13:10:14 stretch40 weewx[1174] INFO weewx.manager: Added record 2020-
01-23 13:10:00 AEST (1
On Wednesday, January 22, 2020 at 8:20:57 PM UTC-6, Thomas Keffer wrote:
>
> Thanks, Paul
>
> Could you temporarily replace your copy of units.py with the attached? It
> will log some clues about what's causing the decode error.
>
>
>
>
TK: Wilco - but tomorrow (sorry for delay).
Thanks!
P.
-
Hmm, noticed the same error on my 4.0/python 2 VM. All was fine around 10am
my time on 20 January and the error is there 9am on 21 January. This VM is
not run continuously but shutdown at night and started each time it's
needed. The first thing after startup is a git pull from development. When
Thanks, Paul
Could you temporarily replace your copy of units.py with the attached? It
will log some clues about what's causing the decode error.
On Wed, Jan 22, 2020 at 6:04 PM P Simmons wrote:
> Howdy! I had no problems using v4.0.0b6 but decided to upgrade to v4.0.0b9.
>
> I'm now having p
Howdy! I had no problems using v4.0.0b6 but decided to upgrade to v4.0.0b9.
I'm now having problems with report generation.
Here are my (sanitized) conf and log files.
Thank you,
Paul
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscri
20 matches
Mail list logo
