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 before I restart my Python script under a debugger. Thus I require owserver, thus any of the direct bindings is a no-go. Also, owserver is long-running; connecting to it is nearly instantaneous and does not require privileges. Starting a script that loads owlib in order to access the bus directly, not so much. Also², async usage of owlib requires multithreading AFAIK, or at least specialized code. With owserver I can write a reasonably-simple protocol handler, throw the request packet to owserver, and process the answer whenever I feel like doing so. NB: Python3 support has landed in SWIG 1.3.37, sometime in 2008 … obviously those were the days before Semantic Versioning got any kind of traction, but that's a different problem. :-P -- -- Matthias Urlichs ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
