From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] nmbug: explicitly prefer python3
Date: Thu, 12 Mar 2020 00:58:23 -0400 [thread overview]
Message-ID: <87r1xyp3tc.fsf@fifthhorseman.net> (raw)
In-Reply-To: <20180209043211.4792-1-dkg@fifthhorseman.net>
[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]
Two years later, I'd like to re-propose this patch that moves nmbug to
python3.
I have read what PEP 394 says (thanks for the pointer, Trevor!) but in
practice (a) i do not see debian pointing /usr/bin/python to python3 any
time in the near future, (b) python2 is officially EOL, and (c) i don't
have a "python" binary in my $PATH at all any more on the machines where
i do most of my development work.
Can we please just be done with requiring people who actively develop
notmuch to keep python 2 installed, or to point some other element named
python maintained in their path ?
--dkg
On Thu 2018-02-08 23:32:11 -0500, Daniel Kahn Gillmor wrote:
> nmbug and notmuch-report are developer tools. It's 2018, and all
> developers should have python3 available.
>
> Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
> ---
> devel/nmbug/nmbug | 2 +-
> devel/nmbug/notmuch-report | 5 ++---
> 2 files changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/devel/nmbug/nmbug b/devel/nmbug/nmbug
> index c35dd75d..043c1863 100755
> --- a/devel/nmbug/nmbug
> +++ b/devel/nmbug/nmbug
> @@ -1,4 +1,4 @@
> -#!/usr/bin/env python
> +#!/usr/bin/env python3
> #
> # Copyright (c) 2011-2014 David Bremner <david@tethera.net>
> # W. Trevor King <wking@tremily.us>
> diff --git a/devel/nmbug/notmuch-report b/devel/nmbug/notmuch-report
> index a9c2a6ec..a4c13939 100755
> --- a/devel/nmbug/notmuch-report
> +++ b/devel/nmbug/notmuch-report
> @@ -1,10 +1,9 @@
> -#!/usr/bin/python
> +#!/usr/bin/env python3
> #
> # Copyright (c) 2011-2012 David Bremner <david@tethera.net>
> #
> # dependencies
> -# - python 2.6 for json
> -# - argparse; either python 2.7, or install separately
> +# - python3 or python2.7
> #
> # This program is free software: you can redistribute it and/or modify
> # it under the terms of the GNU General Public License as published by
> --
> 2.15.1
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> https://notmuchmail.org/mailman/listinfo/notmuch
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-03-12 12:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 4:32 [PATCH] nmbug: explicitly prefer python3 Daniel Kahn Gillmor
2018-02-09 17:12 ` W. Trevor King
2018-02-09 18:36 ` Daniel Kahn Gillmor
2018-02-09 20:46 ` W. Trevor King
2018-02-12 3:56 ` Daniel Kahn Gillmor
2018-02-12 17:53 ` W. Trevor King
2018-02-15 5:37 ` Tomi Ollila
2018-02-15 18:34 ` W. Trevor King
2018-02-18 4:42 ` Daniel Kahn Gillmor
2020-03-12 4:58 ` Daniel Kahn Gillmor [this message]
2020-03-12 16:57 ` Tomi Ollila
2020-03-24 13:42 ` Daniel Kahn Gillmor
2020-04-03 13:33 ` 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=87r1xyp3tc.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.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).