From: "W. Trevor King" <wking@tremily.us>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] nmbug: explicitly prefer python3
Date: Fri, 9 Feb 2018 09:12:57 -0800 [thread overview]
Message-ID: <20180209171257.GG30368@valgrind.us> (raw)
In-Reply-To: <20180209043211.4792-1-dkg@fifthhorseman.net>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
On Thu, Feb 08, 2018 at 11:32:11PM -0500, Daniel Kahn Gillmor wrote:
> nmbug and notmuch-report are developer tools. It's 2018, and all
> developers should have python3 available.
From PEP 394 [1]:
One exception to this is scripts that are deliberately written to be
source compatible with both Python 2.x and 3.x. Such scripts may
continue to use python on their shebang line without affecting their
portability.
So while everyone who uses nmbug may have python3, I don't see a need
to pick sides. Is there something using python3 gets you for nmbug
that you miss with python2?
Cheers,
Trevor
[1]: https://www.python.org/dev/peps/pep-0394/#recommendation
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-09 17:22 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 [this message]
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
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=20180209171257.GG30368@valgrind.us \
--to=wking@tremily.us \
--cc=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).