From: Ian Campbell <ian.campbell@citrix.com>
To: Martin Cerveny <M.Cerveny@computer.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: Status of python libxl bindings
Date: Sat, 23 Aug 2014 16:35:23 +0100 [thread overview]
Message-ID: <1408808123.30706.11.camel@citrix.com> (raw)
In-Reply-To: <alpine.GSO.2.00.1408231403100.9183@dmz.c-home.cz>
On Sat, 2014-08-23 at 14:12 +0200, Martin Cerveny wrote:
> Hello.
>
> I see that binding was disabled by 2012 ( http://lists.xen.org/archives/html/xen-devel/2012-07/msg01297.html ).
>
> Is there any functional libxl-python bindings ?
Not as far as I know, the in tree ones are IMHO broken at the design
level, but also they don't compile either...
> ( or use another toolstack - like python bindings for libvirt-libxl ? )
I don't know about libvirt language bindings but I would expect that no
specific libvirt-libxl bindings would be needed, so if you have Python
bindings for libvirt I expect they should be expected to work regardless
of the backend.
Ian.
next prev parent reply other threads:[~2014-08-23 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 12:12 Status of python libxl bindings Martin Cerveny
2014-08-23 15:35 ` Ian Campbell [this message]
2014-08-27 22:28 ` Jim Fehlig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1408808123.30706.11.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=M.Cerveny@computer.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).