Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

2017-12-17 Thread HW
Stefano and the others who also responded, Thanks very much for your clarification of this problem and especially for the detailed suggestions on how to move forward! -- Check out the vibrant tech community on one of th

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

2017-12-17 Thread Matthias Urlichs via Owfs-developers
On 17.12.2017 17:45, Gregg Levine wrote: > Of course the merely obvious question is why the swig bindings are not > under active development. Because they're mosty useless, IMHO. In any sort off production environment I want a way to access the actual bus and check which data is actually out there

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

2017-12-17 Thread Tomasz Torcz 👁️
On Sun, Dec 17, 2017 at 04:58:15PM +0100, Matthias Urlichs via Owfs-developers wrote: > On 17.12.2017 00:19, Stefano Miccoli wrote: > > Unfortunately owpython (the swig bindings) is not under active > > development. > > I'd go a step further and remove them from the next release. +1 from me! T

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

2017-12-17 Thread Jan Kandziora
Am 17.12.2017 um 17:45 schrieb Gregg Levine: > Hello! > I'd go a bigger step further and make them optional by way of how the > configure script is managed. I manage three platforms here. My desktop > a 32 bit machine running Slackware 11.0 Linux, and this laptop, that > also runs Slackware 14.2 in

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

2017-12-17 Thread Colin Reese
I do exclusively. I was using my own wrapper reading directories but now use pyownet. C > On Dec 17, 2017, at 8:45 AM, Gregg Levine wrote: > > Hello! > I'd go a bigger step further and make them optional by way of how the > configure script is managed. I manage three platforms here. My deskto

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

2017-12-17 Thread Gregg Levine
Hello! I'd go a bigger step further and make them optional by way of how the configure script is managed. I manage three platforms here. My desktop a 32 bit machine running Slackware 11.0 Linux, and this laptop, that also runs Slackware 14.2 in 64 bit mode. And of course any number of Raspberry Pi

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

2017-12-17 Thread Matthias Urlichs via Owfs-developers
On 17.12.2017 00:19, Stefano Miccoli wrote: > Unfortunately owpython (the swig bindings) is not under active > development. I'd go a step further and remove them from the next release. -- -- Matthias Urlichs -- Check o

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

2017-12-16 Thread Stefano Miccoli
Unfortunately owpython (the swig bindings) is not under active development. The current best practice is to *always* run owserver on the host with the one-wire bus master, and have all clients access the one-wire bus via the owserver protocol. My personal suggestion is to take the time to try o

[Owfs-developers] python-ow failure with new Raspbian Stretch

2017-12-15 Thread HW
Using a DS9490, I have been running the python based Weewx weather station software for several years on the Raspbian Wheezy OS. Unfortunately, the same program is failing on the new Raspbian Stretch OS and can be verified with a simple test case. Run the following program as root (to bypass any