From: Florian Friesdorf <flo@chaoflow.net>
To: Sebastian Spaeth <Sebastian@SSpaeth.de>,
Jameson Rollins <jrollins@finestructure.net>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: python documentation
Date: Mon, 18 Apr 2011 17:03:01 +0200 [thread overview]
Message-ID: <87hb9v61qy.fsf@eve.chaoflow.net> (raw)
In-Reply-To: <877har7jcp.fsf@SSpaeth.de>
[-- Attachment #1: Type: text/plain, Size: 1722 bytes --]
On Mon, 18 Apr 2011 15:57:26 +0200, Sebastian Spaeth <Sebastian@SSpaeth.de> wrote:
> On Mon, 18 Apr 2011 14:32:16 +0200, Florian Friesdorf <flo@chaoflow.net> wrote:
> > I think it is confusing that it has a different versioning than notmuch
> > itself and that it would be more intuitive if the current bindings on
> > pypi [1] would have the same version as the current stable release of
> > notmuch.
>
> But that would require that the python bindings are actually updated to
> the current API of notmuch :-). Because they currently are not. E.g. the
> get_filename/get_filenames addition is still not included.
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.
Naïvely, I imagine there is a header file and the generation of the
python bindings happens rather automagic.
> > If they would also work with older releases of notmuch, that
> > could still be indicated, as it is done now.
>
> As far as for testing current implementations with older notmuch
> libraries, I welcome people to contribute patches to the documentation
> because I certainly will not test all combinations :-).
>
> To be honest, I don't even use the python bindings anymore, not that
> notmuch proper is able to give me all I need (especially file names).
Point taken, I don't use them yet, I might in the future.
--
Florian Friesdorf <flo@chaoflow.net>
GPG FPR: 7A13 5EEE 1421 9FC2 108D BAAF 38F8 99A3 0C45 F083
Jabber/XMPP: flo@chaoflow.net
IRC: chaoflow on freenode,ircnet,blafasel,OFTC
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-04-18 15:03 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 [this message]
2011-04-19 20:01 ` Sebastian Spaeth
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=87hb9v61qy.fsf@eve.chaoflow.net \
--to=flo@chaoflow.net \
--cc=Sebastian@SSpaeth.de \
--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).