On 12/01/16 20:13, W. Trevor King wrote:
On Tue, Jan 12, 2016 at 03:03:15PM -0400, David Bremner wrote:
Nothing to do with Konrad's crash, but I consider the fact that the
python bindings read ~/.notmuch-config to be a kind of layering
violation, since that file belongs to the CLI, while the bi
Hi Justus,
> So I guess what happens is that Python3 changed how the interpreter
> environment is torn down and they actually destroy the 'q' object. If
> that is so, then your data is indeed safe.
That reminds me of a recent change in object finalization in Python 3:
https://www.python.org/d
David Bremner 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
Hi everyone,
I have been writing quite a few Python scripts for notmuch before
running into a strange bug. Here is a minimal script producing it:
--
from notmuch import Query, Database
def foo(bar):
pass
db = Database()
q = Query(db, "*")
d
Hi everyone,
while looking for the latest source for checking if my recent bug report
still applies, I noticed that the README for the Python bindings is
hopelessly outdated. It refers to a bitbucket repository that hasn't
been updated since 2010. Moreover, it recommends installing from PyPI,
