unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Sebastian Spaeth <Sebastian@SSpaeth.de>
To: Florian Friesdorf <flo@chaoflow.net>,
	Jameson Rollins <jrollins@finestructure.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: python documentation
Date: Tue, 19 Apr 2011 22:01:54 +0200	[thread overview]
Message-ID: <87oc4257t9.fsf@SSpaeth.de> (raw)
In-Reply-To: <87hb9v61qy.fsf@eve.chaoflow.net>

[-- Attachment #1: Type: text/plain, Size: 710 bytes --]

On Mon, 18 Apr 2011 17:03:01 +0200, Florian Friesdorf <flo@chaoflow.net> wrote:
> Is it sane to have python bindings that need updates or would a plain
> wrapper of the notmuch script (that maybe needs less updates) be better?
> I don't want to imply that this can be answered with yes/no, but more to
> get a comparison of the two approaches.

Invoking notmuch the script and piping the results? I wouldn't call that
python bindings anymore then. Also it is bound to be much more expensive
than directly interfacing libnotmuch.so.

> Naïvely, I imagine there is a header file and the generation of the
> python bindings happens rather automagic.

I wish it would be that easy. :-)

Sebastian

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2011-04-19 20:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15  6:26 python documentation Jameson Rollins
2011-03-15 15:16 ` Sebastian Spaeth
2011-03-15 18:22   ` James Vasile
2011-03-15 18:33     ` Jameson Rollins
2011-03-15 19:01       ` James Vasile
2011-03-16  9:17         ` Sebastian Spaeth
2011-04-18 12:32   ` Florian Friesdorf
2011-04-18 13:57     ` Sebastian Spaeth
2011-04-18 15:03       ` Florian Friesdorf
2011-04-19 20:01         ` Sebastian Spaeth [this message]
2011-04-19 20:35           ` Aaron Williamson

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oc4257t9.fsf@SSpaeth.de \
    --to=sebastian@sspaeth.de \
    --cc=flo@chaoflow.net \
    --cc=jrollins@finestructure.net \
    --cc=notmuch@notmuchmail.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).