unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Patrick Totzke <patricktotzke@googlemail.com>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: notmuch as a shared object aka library knigge
Date: Tue, 21 Feb 2012 15:35:42 +0000	[thread overview]
Message-ID: <20120221153542.29533.62958@megatron> (raw)
In-Reply-To: <20120221002921.8534.57091@thinkbox.jade-hamburg.de>

Hi all,

Those of you with long enough backlog on the list to remember my rant (id:20110626202733.GA26837@brick)
can guess my opion on this matter but just to be sure..

I am not much of an expert on libnotmuch internals but am using the python bindings extensively.
It feels super-strange using a python module that possibly writes to stderr or any other descriptor
without me explicitly telling it to.
Also, if the library segfauls or calls exit, it essentially rips out the python interpreter underneath my code
without me being able to do any proper error handling.

I know that error handling on a library level is hard, juggling around with bare C, talloc and Xapian.
But i can only strongly encourage any rewrite that ends in the python bindings behaving more pythonic!

Cheers,
/p

  reply	other threads:[~2012-02-21 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-21  0:29 notmuch as a shared object aka library knigge Justus Winter
2012-02-21 15:35 ` Patrick Totzke [this message]
2012-02-21 15:53 ` Austin Clements
2012-02-22 15:17   ` Justus Winter
2012-02-23 22:22     ` Justus Winter
2012-02-24  0:29       ` David Bremner
2012-02-24  1:04         ` Justus Winter
2012-02-24  0:33       ` David Bremner
2012-02-24  1:08         ` Justus Winter

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=20120221153542.29533.62958@megatron \
    --to=patricktotzke@googlemail.com \
    --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).