Re: [weewx-development] error in setup.py after update to commit 4a36cbf

2019-11-26 Thread Thomas Keffer
Not a changed requirement. setup.py has import configobj since at least V1.2.0. Maybe earlier. On Tue, Nov 26, 2019 at 9:16 AM P Simmons wrote: > Tom, Vince... gracias, was unaware of the changed requirement. Yo soy un > viejo. > > Paul > > -- > You received this message because you are

Re: [weewx-development] error in setup.py after update to commit 4a36cbf

2019-11-26 Thread Vince Skahan
On Tuesday, November 26, 2019 at 9:26:08 AM UTC-8, P Simmons wrote: > On Tuesday, November 26, 2019 at 11:16:52 AM UTC-6, P Simmons wrote: >> >> Tom, Vince... gracias, was unaware of the changed requirement. Yo soy un >> viejo. >> >> Or, perhaps my distro changed to python 3 as default... >

Re: [weewx-development] error in setup.py after update to commit 4a36cbf

2019-11-26 Thread P Simmons
On Tuesday, November 26, 2019 at 11:16:52 AM UTC-6, P Simmons wrote: > > Tom, Vince... gracias, was unaware of the changed requirement. Yo soy un > viejo. > > Paul > > Or, perhaps my distro changed to python 3 as default... -- You received this message because you are subscribed to the

Re: [weewx-development] error in setup.py after update to commit 4a36cbf

2019-11-26 Thread P Simmons
Tom, Vince... gracias, was unaware of the changed requirement. Yo soy un viejo. Paul -- 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

Re: [weewx-development] error in setup.py after update to commit 4a36cbf

2019-11-26 Thread Thomas Keffer
The source build package uses configobj (so it can check weewx.conf for errors). So, even though you're only packaging, and not deploying, you need configobj installed on your first machine. -tk On Tue, Nov 26, 2019 at 5:53 AM P Simmons wrote: > For my own arcane reasons, I prefer to build on

[weewx-development] error in setup.py after update to commit 4a36cbf

2019-11-26 Thread P Simmons
For my own arcane reasons, I prefer to build on one machine using "make src-package", and transferring the resulting "./dist/*.gz" to another. After a "git pull" updating to commit 4a36cbf, I get the following output: ./setup.py sdist Traceback (most recent call last): File "./setup.py", line