All of lore.kernel.org
 help / color / mirror / Atom feed
From: Killian De Volder <killian.de.volder@megasoft.be>
To: lvm-devel@redhat.com
Subject: liblvm Python/C extension (Python Liblvm)
Date: Thu, 22 Mar 2012 08:17:37 +0100	[thread overview]
Message-ID: <4F6AD211.3040807@megasoft.be> (raw)

@Lars,
I'm rather interested in this, have there been any updates ?

@The community,
Are there any plans for allowing python binding in the lvm-sources, or should this be a separate package ?
I also detect no way in lvm2app to create for example a snapshot. So I'm going to assume there is also need for work here.
Or is C binding of LVM generally a bad idea, and should we instead parse the lvm-tool output and communicate with LVM trough those means ?

Feedback is welcome of course.

Kind regards,
Killian De Volder

>  Hello,
>
>  I was missing a proper LVM2 interface to Python so I decided to write
>  one my self! I have wrapped all the liblvm C APIs (excluding the new
>  APIs committed in Dec). Doc strings are still missing, as well as proper
>  setup.py build env, so consider it as work in progress.
>
>  This might also be interesting to other projects like Anaconda for
>  example.
>
>  I would love to get your feedback on it!
>
>  Best regards,
>  Lars



             reply	other threads:[~2012-03-22  7:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22  7:17 Killian De Volder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-01-20 12:49 liblvm Python/C extension (Python Liblvm) Lars Sjöström
2011-01-20 15:24 ` Zdenek Kabelac
2011-01-24  0:11 ` Petr Rockai
2011-01-24  9:58   ` Lars Sjöström
2011-01-24 10:10     ` Zdenek Kabelac
2011-01-24 10:08   ` Zdenek Kabelac

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=4F6AD211.3040807@megasoft.be \
    --to=killian.de.volder@megasoft.be \
    --cc=lvm-devel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.