Andy,
yes, in this case we would control both sides of the story. I
believe we can also package the C client library within the Python
distribution package, and tell the Python bindings to use the
included client library. That way, when someone installs the
Python package, they get the whole deal, no external
requirements. When they upgrade the Python package, both bindings
and client library are updated at the same time.
b) There is a possibility of a pure Python client, but this is
quicker!
Ian
On 20/03/13 16:29,
andypiperuk@xxxxxxxxx wrote:
For reasons why I'm in favour of a pure Python / no
C dependency if possible (the ease of implementation of the
latter notwithstanding), I follow the "other" MQ Python bindings
project - pymqi for WMQ - and I know that new releases of MQ
libs cause compatibility issues (see
https://bugs.launchpad.net/pymqi/+bug/1060771)
I realise that we'd control both sides of the
story in this case, but it does highlight that a standalone
Python implementation is nicer.
Having said all of that, if it's easy to
contribute something that binds to the C library then I'm also
in favour of getting as much code "out there" as possible :-)
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev