unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Justus Winter <justus@gnupg.org>
To: David Bremner <david@tethera.net>,
	Sebastian Spaeth <Sebastian@SSpaeth.de>,
	Aryeh Leib Taurog <python@aryehleib.com>
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch version/Python bindings
Date: Mon, 20 Feb 2017 12:39:00 +0100	[thread overview]
Message-ID: <877f4lum5n.fsf@europa.jade-hamburg.de> (raw)
In-Reply-To: <87mvdj8r9y.fsf@tethera.net>

[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]

David Bremner <david@tethera.net> writes:

> Sebastian Spaeth <Sebastian@SSpaeth.de> writes:
>
>> Hi there, I did stop using notmuch, true. Let me know if I should hand
>> over administration or if I shouldnsimply delete the package on pypi.
>>
>
> Hi Sebastian;
>
> Thanks for the followup.  If no-one steps up to maintain by the end of
> next week, I'd say just delete them from pypi.
>
> I don't really think that "the notmuch project" needs to be involved in
> deciding who, if anyone, maintains a pypi package (anymore than we
> micromanage who maintains notmuch in various linux distros). I have a
> vague memory that Justus (nominally in charge of the python bindings)
> was not interested in pypi, but I could be wrong. In any case Justus not
> very active lately either.

No, I'm really not, sorry.

Somewhat related, I adopted the Python bindings for GPGME, and I was
convinced by Python users that publishing on pypi is important for the
bindings to be used.  However, we also have the problem of people trying
to build the bindings from pypi with older versions of the library, and
one person actually suggested to build the library itself as part of
building the binginds to work around that.

Nowadays I tend to think that it is better to distribute the bindings
through the same channels as the library.


Justus



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2017-02-20 11:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 14:09 notmuch version/Python bindings Aryeh Leib Taurog
2017-02-16 14:24 ` David Bremner
2017-02-16 14:58   ` Aryeh Leib Taurog
2017-02-16 17:00     ` David Bremner
2017-02-16 19:46       ` Sebastian Spaeth
2017-02-18 15:14         ` David Bremner
2017-02-20 11:39           ` Justus Winter [this message]
2017-02-21 14:03           ` Sebastian Spaeth
2017-02-25 16:41             ` David Bremner

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=877f4lum5n.fsf@europa.jade-hamburg.de \
    --to=justus@gnupg.org \
    --cc=Sebastian@SSpaeth.de \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    --cc=python@aryehleib.com \
    /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).