On Tue, Sep 03, 2013 at 02:13:58PM +0200, Nicolas Sebrecht wrote: > The 03/09/13, Daniel P. Berrange wrote: > > > Err, what API changes are you talking about ? Both the libvirt C API, > > and any language bindings, including the python, are intended to be long > > term stable APIs. We only ever add new APIs or flags - never change > > existing APis. > > I can't give a precise example, sorry. I had a wrong surprise in the > late 2010 and since kept far from the python bindings. I might change to > rely on the bindings if you actually think APIs are long term stable. They have always been stable & will continue to be stable. Of course sometimes there may be bugs in particular releases that get fixed, but that's normal & would not be changing the semantics of the APIs in an backwards-incompatible manner. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list