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
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
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
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
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!
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
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