unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Floris Bruynooghe <flub@devork.be>
To: "David Bremner" <david@tethera.net>,
	"Brian May" <brian@linuxpenguins.xyz>,
	"David Čepelík" <d@dcepelik.cz>,
	notmuch@notmuchmail.org
Subject: Re: segfault using python bindings
Date: Fri, 16 Nov 2018 22:39:22 +0100	[thread overview]
Message-ID: <87pnv4bt2t.fsf@powell.devork.be> (raw)
In-Reply-To: <87zhu9tixf.fsf@tethera.net>

On Fri 16 Nov 2018 at 06:29 -0400, David Bremner wrote:

> Brian May <brian@linuxpenguins.xyz> writes:
>
>> Floris Bruynooghe <flub@devork.be> writes:
>>
>>> I've since wondered if just getting them standalone on pypi is perhaps a
>>> useful service in the mean time as it's relatively little effort.  And
>>> if there eventually is a desire again to get them merged in some way
>>> that could still be done.
>>
>> Standalone on pypi would be my preferred option.
>>
>> It is defacto Python standard to refer to all dependancies in something
>> like requirements.txt or Pipfile from pypi.
>
> As I mentioned last time this was discussed, the python bindings are
> currently more or less a core part of notmuch as both the test
> suite and developement need them.

Sure, I think pypi publishing is orthogonal to this however.  Either or
both versions of the bindings could be published on pypi in addition to
being in the main repo.  As Brian mentions it would improve
discoverability and improves integration on the python side.  There's
even tooling to bundle the library these days with the manylinux1
wheels.  So there's no need to stop anyone who'd like to do this.

  reply	other threads:[~2018-11-16 21:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 14:49 segfault using python bindings David Čepelík
2018-11-11 20:16 ` David Bremner
2018-11-11 20:21   ` Gaute Hope
2018-11-15 21:13   ` Floris Bruynooghe
2018-11-16  4:44     ` Brian May
2018-11-16 10:29       ` David Bremner
2018-11-16 21:39         ` Floris Bruynooghe [this message]
2018-11-17  0:15           ` David Bremner
2018-11-16 10:27     ` David Bremner
2018-11-16 12:15       ` Daniel Kahn Gillmor
2018-11-16 22:07         ` Floris Bruynooghe
2019-08-14 19:20     ` David Bremner
2019-08-15  9:53       ` Floris Bruynooghe
2019-08-15 12:28         ` David Bremner
2019-08-20 17:20           ` Floris Bruynooghe
2019-08-21 16:02             ` Daniel Kahn Gillmor
2019-08-22 19:24               ` David Bremner
2019-08-22 19:37                 ` Rollins, Jameson
2019-08-23  0:09                   ` David Bremner
2019-08-23  1:59                   ` Daniel Kahn Gillmor
2019-08-23 12:07                     ` David Bremner
2019-08-23 20:43                       ` Daniel Kahn Gillmor
2019-08-23 22:58                         ` Rollins, Jameson
2019-08-26 17:09               ` Floris Bruynooghe
2019-08-26 17:28                 ` David Bremner
2018-11-18 20:22 ` Dirk Van Haerenborgh
2018-11-18 23:34   ` David Bremner
2018-11-19  9:09     ` Dirk Van Haerenborgh

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=87pnv4bt2t.fsf@powell.devork.be \
    --to=flub@devork.be \
    --cc=brian@linuxpenguins.xyz \
    --cc=d@dcepelik.cz \
    --cc=david@tethera.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).