All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: liblvm Python/C extension (Python Liblvm)
Date: Mon, 24 Jan 2011 11:08:13 +0100	[thread overview]
Message-ID: <4D3D4F8D.5090305@redhat.com> (raw)
In-Reply-To: <87oc77tb33.fsf@twilight.int.mornfall.net.>

Dne 24.1.2011 01:11, Petr Rockai napsal(a):
> Hi,
> 
> Lars Sj?str?m <lars.sjostrom@redhat.com> writes:
>> 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!
> 
> I am not a python guy myself, but I definitely welcome this. On the
> other hand, as Zden?k points out, this does have some issues. I also
> think Anaconda folks have refused to use liblvm as far as there are no
> python bindings (and they are not interested in binding to the C API
> themselves). Hence, I suppose they are going to be interested indeed.
> 

I'm trying to get Anaconda team requirements in some written form - they are
doing many weird things which needs to be sorted out (currently they use some
rather very ugly hacks in their code) - I believe they do not need to handle
things in python at all as they do now and they should be happy with lvm2cmd
library - IMHO they need some virtual LVM support - but let's wait what will
they provide to us.

Zdenek



  parent reply	other threads:[~2011-01-24 10:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-03-22  7:17 Killian De Volder

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=4D3D4F8D.5090305@redhat.com \
    --to=zkabelac@redhat.com \
    --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.