On Sat, 23 Jul 2011 14:36:02 +0100, Patrick Totzke wrote:
> I hope the patch I send is correctly formated, I'm still fumbling with
> git send-email and the --in-reply-to option.
> Anyhow, forgive my language, of course I didn't mean to be condescending in
> any
> way by calling these prints garbag
On Sat, 23 Jul 2011 14:36:02 +0100, Patrick Totzke wrote:
> I hope the patch I send is correctly formated, I'm still fumbling with
> git send-email and the --in-reply-to option.
> Anyhow, forgive my language, of course I didn't mean to be condescending in
> any
> way by calling these prints garbag
Hi all,
I hope the patch I send is correctly formated, I'm still fumbling with
git send-email and the --in-reply-to option.
Anyhow, forgive my language, of course I didn't mean to be condescending in any
way by calling these prints garbage! It's just that it's highly unusual and very
'non-pythonic
Hi all,
I hope the patch I send is correctly formated, I'm still fumbling with
git send-email and the --in-reply-to option.
Anyhow, forgive my language, of course I didn't mean to be condescending in any
way by calling these prints garbage! It's just that it's highly unusual and very
'non-pythonic
Hi all,
I know this issue is not easy to fix and that it's partly a problem
with xapians bad error handling. I just want to state another problem we run
into with xapians exceptions in combination with the python bindings.
If you run the following snippet, you notice that not only do we get
xapian
On Sun, 17 Jul 2011 20:35:38 +0100, Patrick Totzke wrote:
> If you run the following snippet, you notice that not only do we get
> xapian-garbage on stderr but we don't really get any exceptions at the
> position where it would make sense:
I wouldn't call that "xapian-garbage" since it is output
On Sun, 17 Jul 2011 20:35:38 +0100, Patrick Totzke
wrote:
> If you run the following snippet, you notice that not only do we get
> xapian-garbage on stderr but we don't really get any exceptions at the
> position where it would make sense:
I wouldn't call that "xapian-garbage" since it is output
Hi all,
I know this issue is not easy to fix and that it's partly a problem
with xapians bad error handling. I just want to state another problem we run
into with xapians exceptions in combination with the python bindings.
If you run the following snippet, you notice that not only do we get
xapian
Hi all!
It's me again, with some strange python behaviour :/
When I iterate over threads or messages only partially,
then make changes to the index and continue the iteration,
then I don't necessarily get NotmuchError's but the underlying
libnotmuch seems to call terminate. I get the following two
Hi all!
It's me again, with some strange python behaviour :/
When I iterate over threads or messages only partially,
then make changes to the index and continue the iteration,
then I don't necessarily get NotmuchError's but the underlying
libnotmuch seems to call terminate. I get the following two
10 matches
Mail list logo
