Re: Usage after database close

2020-06-29 Thread Floris Bruynooghe
On Sun 28 Jun 2020 at 19:11 -0300, David Bremner wrote: > You need to add a seperate repo for the new style debug symbols in > Debian: > $ (git)-[master]-% apt policy libxapian30-dbgsym > libxapian30-dbgsym: > Installed: 1.4.15-1 > Candidate: 1.4.15-1 > Version table: > *** 1.4.15-1 500 >

Re: Usage after database close

2020-06-29 Thread David Bremner
David Bremner writes: > David Bremner writes: > > >>> But part of my question is, *should* this be improved? Am I >>> interpreting notmuch's intended API correctly? >> >> Well, I agree you should get NOTMUCH_STATUS_XAPIAN_EXCEPTION back, or we >> should change the docs to say "just don't do

Re: Usage after database close

2020-06-28 Thread David Bremner
David Bremner writes: >> But part of my question is, *should* this be improved? Am I >> interpreting notmuch's intended API correctly? > > Well, I agree you should get NOTMUCH_STATUS_XAPIAN_EXCEPTION back, or we > should change the docs to say "just don't do that". Arguments in favour of the

Re: Usage after database close

2020-06-28 Thread David Bremner
Floris Bruynooghe writes: > > Ok, I forgot the "expected behaviour" part of the bug report ;) I think > that this doesn't work is fine and I'm not surprised by and your > description of fetching it first is very reasonable. However I was > expecting NOTMUCH_STATUS_XAPIAN_EXEPTION instead of

Re: Usage after database close

2020-06-28 Thread Floris Bruynooghe
On Sun 28 Jun 2020 at 13:19 -0300, David Bremner wrote: > Floris Bruynooghe writes: > >> Hi, >> >> I started writing some test cases to define better what you can do with >> a closed database and make sure that the python bindings do not behave >> unexpectedly here too. >> >> One of the first

Re: Usage after database close

2020-06-28 Thread David Bremner
Floris Bruynooghe writes: > Hi, > > I started writing some test cases to define better what you can do with > a closed database and make sure that the python bindings do not behave > unexpectedly here too. > > One of the first things I tried ends up with xapian calling > exit_group(2) directly,