All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Rockai <prockai@redhat.com>
To: lvm-devel@redhat.com
Subject: liblvm Python/C extension (Python Liblvm)
Date: Mon, 24 Jan 2011 01:11:12 +0100	[thread overview]
Message-ID: <87oc77tb33.fsf@twilight.int.mornfall.net.> (raw)
In-Reply-To: <1295527769.24069.31.camel@ljonsson.local> ("Lars Sjöström"'s message of "Thu, 20 Jan 2011 13:49:29 +0100")

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.

Nevertheless, there's another significant issue, and that is
maintenance. I can't commit to maintaining python bindings, since I have
responsibilities besides liblvm and I am a part-timer on LVM -- which
doesn't exactly leave much space for python (which would necessarily
include a lot of learning).

I'll try to talk with the rest of the team about how to best approach
this. There might be someone with the required python (and python
binding) skills and enough time. Alternatively, do you think you could
take the responsibility for the bindings yourself? As far as I recall,
there was talk of shipping python bindings (provided there were any, but
you obviously have some now) with the rest of LVM source (although I
have no idea what technical implications this may have for building
packages).

Yours,
   Petr



  parent reply	other threads:[~2011-01-24  0:11 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 [this message]
2011-01-24  9:58   ` Lars Sjöström
2011-01-24 10:10     ` Zdenek Kabelac
2011-01-24 10:08   ` Zdenek Kabelac
  -- 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=87oc77tb33.fsf@twilight.int.mornfall.net. \
    --to=prockai@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.