Re: Python binding SIGABRT/SIGSEGV

2022-02-16 Thread Floris Bruynooghe
On Thu 10 Feb 2022 at 13:16 +0100, Michael J Gruber wrote: > Austin Lund venit, vidit, dixit 2022-02-10 06:56:12: >> I'm clearly doing this python code wrong by not using the iterator correctly: >> >> > import notmuch2 >> > >> > d = notmuch2.Database() >> > m = list(d.messages("since:today"))

Re: Python binding SIGABRT/SIGSEGV

2022-02-11 Thread Tomi Ollila
On Fri, Feb 11 2022, Michael J. Gruber wrote: > Austin Lund venit, vidit, dixit 2022-02-10 23:21:58: >> On Thu, Feb 10, 2022 at 01:12:47PM +0100, Michael J Gruber wrote: >> > Austin Lund venit, vidit, dixit 2022-02-10 06:56:12: >> > > I'm clearly doing this python code wrong by not using the

Re: Python binding SIGABRT/SIGSEGV

2022-02-11 Thread Michael J Gruber
Austin Lund venit, vidit, dixit 2022-02-10 23:21:58: > On Thu, Feb 10, 2022 at 01:12:47PM +0100, Michael J Gruber wrote: > > Austin Lund venit, vidit, dixit 2022-02-10 06:56:12: > > > I'm clearly doing this python code wrong by not using the iterator > > > correctly: > > > > > > > import

Re: Python binding SIGABRT/SIGSEGV

2022-02-10 Thread Austin Lund
On Thu, Feb 10, 2022 at 01:12:47PM +0100, Michael J Gruber wrote: > Austin Lund venit, vidit, dixit 2022-02-10 06:56:12: > > I'm clearly doing this python code wrong by not using the iterator > > correctly: > > > > > import notmuch2 > > > > > > d = notmuch2.Database() > > > m =

Re: Python binding SIGABRT/SIGSEGV

2022-02-10 Thread Michael J Gruber
Austin Lund venit, vidit, dixit 2022-02-10 06:56:12: > I'm clearly doing this python code wrong by not using the iterator correctly: > > > import notmuch2 > > > > d = notmuch2.Database() > > m = list(d.messages("since:today")) > > p = m[0].path > > print(p) > > But I seem to be getting a

Python binding SIGABRT/SIGSEGV

2022-02-10 Thread Austin Lund
I'm clearly doing this python code wrong by not using the iterator correctly: > import notmuch2 > > d = notmuch2.Database() > m = list(d.messages("since:today")) > p = m[0].path > print(p) But I seem to be getting a SIGABRT instead of a python stack trace. Is this the expected behaviour?