From: Aryeh Leib Taurog <python@aryehleib.com>
To: David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch version/Python bindings
Date: Thu, 16 Feb 2017 16:58:50 +0200 [thread overview]
Message-ID: <20170216145850.GA2691@deb76.aryehleib.com> (raw)
In-Reply-To: <87h93u9ptb.fsf@tethera.net>
Okay, makes sense. Might I suggest a new release on pypi, then?
On Thu, Feb 16, 2017 at 10:24:16AM -0400, David Bremner wrote:
> Aryeh Leib Taurog <python@aryehleib.com> writes:
>
> > The latest notmuch includes libnotmuch.so.4.4.0 but the latest python
> > bindings wrap libnotmuch.so.3 so importing from notmuch results in the
> > following error:
> >
> > File "/home/altaurog/venv/offlineimap/lib/python2.7/site-packages/notmuch/__init__.py", line 54, in <module>
> > from .database import Database
> > File "/home/altaurog/venv/offlineimap/lib/python2.7/site-packages/notmuch/database.py", line 24, in <module>
> > from .globals import (
> > File "/home/altaurog/venv/offlineimap/lib/python2.7/site-packages/notmuch/globals.py", line 27, in <module>
> > raise ImportError("Could not find shared 'notmuch' library.")
> > ImportError: Could not find shared 'notmuch' library.
> >
> > I changed it to libnotmuch.so.4 in globals.py and it seems to work.
> > Is that reasonable or should I expect problems?
>
> I'd say you should get your python bindings from the same place you get
> libnotmuch. In the latest released source (and in git master), the
> SOVERSION in version.py matches, and globals.py uses that.
>
> d
next prev parent reply other threads:[~2017-02-16 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 14:09 notmuch version/Python bindings Aryeh Leib Taurog
2017-02-16 14:24 ` David Bremner
2017-02-16 14:58 ` Aryeh Leib Taurog [this message]
2017-02-16 17:00 ` David Bremner
2017-02-16 19:46 ` Sebastian Spaeth
2017-02-18 15:14 ` David Bremner
2017-02-20 11:39 ` Justus Winter
2017-02-21 14:03 ` Sebastian Spaeth
2017-02-25 16:41 ` David Bremner
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=20170216145850.GA2691@deb76.aryehleib.com \
--to=python@aryehleib.com \
--cc=david@tethera.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).