From: David Bremner <david@tethera.net>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>, notmuch@notmuchmail.org
Subject: Re: Crash with Python bindings
Date: Tue, 12 Jan 2016 11:26:35 -0400 [thread overview]
Message-ID: <8737u26cpg.fsf@zancas.localnet> (raw)
In-Reply-To: <m160yyev4o.fsf@fastmail.net>
Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
> David Bremner <david@tethera.net> writes:
>
>>> from notmuch import Query, Database
>>>
>>> def foo(bar):
>>> pass
>>>
>>> db = Database()
>>> q = Query(db, "*")
>>> db.close()
>>
>> Do you really call the constructor without a path? Or are you censoring
>> the script for some reason?
>
> No path means path=None, which stands for the path from
> ~/.notmuch-config. That's exactly what I want. Is there some reason not
> to rely on this mechanism?
Oh sorry, I'm (obviously) not that familiar with the python bindings.
d
next prev parent reply other threads:[~2016-01-12 15:26 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 9:41 Crash with Python bindings Konrad Hinsen
2016-01-12 13:11 ` David Bremner
2016-01-12 14:21 ` Konrad Hinsen
2016-01-12 15:26 ` David Bremner [this message]
2016-01-12 19:03 ` David Bremner
2016-01-12 19:13 ` Binding access to ~/.notmuch-config (was: Crash with Python bindings) W. Trevor King
2016-01-13 11:25 ` Binding access to ~/.notmuch-config Konrad Hinsen
2016-01-13 12:25 ` David Bremner
2016-01-13 17:23 ` W. Trevor King
[not found] ` <20160112102329.4269.20741@thinkbox.jade-hamburg.de>
2016-01-12 14:23 ` Crash with Python bindings Konrad Hinsen
2016-01-12 18:51 ` W. Trevor King
2018-03-16 11:59 ` David Bremner
2018-03-16 12:12 ` Justus Winter
2018-03-16 18:30 ` Floris Bruynooghe
2018-03-16 22:40 ` Daniel Kahn Gillmor
2018-03-18 8:01 ` Floris Bruynooghe
2018-03-21 10:16 ` New Python bindings (was: Crash with Python bindings) Justus Winter
2018-03-25 17:40 ` pytest integration for the notmuch test suite David Bremner
2018-03-25 17:40 ` [PATCH 1/3] configure: check for pytest binary David Bremner
2018-03-26 20:55 ` Floris Bruynooghe
2018-03-25 17:40 ` [PATCH 2/3] test: add new test_expect_pytest_success David Bremner
2018-03-25 17:40 ` [PATCH 3/3] test: add example test using pytest David Bremner
2018-03-25 19:14 ` pytest integration for the notmuch test suite Tomi Ollila
2018-03-26 11:31 ` David Bremner
2018-03-26 21:01 ` Floris Bruynooghe
2018-03-26 21:25 ` David Bremner
2018-03-26 20:47 ` New Python bindings (was: Crash with Python bindings) Floris Bruynooghe
2018-03-27 22:29 ` New Python bindings Justus Winter
2018-03-28 22:07 ` Floris Bruynooghe
2018-03-28 7:20 ` New Python bindings (was: Crash with Python bindings) Brian May
2018-03-28 13:42 ` David Bremner
2018-03-28 22:15 ` Floris Bruynooghe
2018-03-28 22:37 ` Brian May
2018-03-28 23:13 ` David Bremner
2018-04-04 22:37 ` Brian May
2018-04-05 1:09 ` Pypi David Bremner
2018-03-28 22:10 ` New Python bindings (was: Crash with Python bindings) Floris Bruynooghe
2016-01-12 18:08 ` Crash with Python bindings W. Trevor King
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=8737u26cpg.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=konrad.hinsen@fastmail.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).