Guy K. Kloss wrote:
Commercial applications still can call it as a black-box application through a system call doing a simple exec.
Right, but they can't package it together without the commercial application becoming subject to the conditions attached to Argyll.
Who says it would need to be a lot of work for Graeme? It's an open source GPL project. So, assuming the coordination between several developers is managed sensibly, the creation of bindings can be handled by other developers. Bindings can be also automagically generated, using e. g. Py++, SWIG (ad done for e. g. OpenCV), or other mechanisms. Just given a talk at the BarCamp Auckland on hybrid Python/C++ development using automatic wrapper generation:
A great deal of the application functionality is actually implemented by the application. It uses various Argyll libraries, but these aren't all of a high enough nature that you'd want to invoke them using Python. Graeme Gill.