unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "W. Trevor King" <wking@tremily.us>
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] nmbug: explicitly prefer python3
Date: Sun, 11 Feb 2018 22:56:36 -0500	[thread overview]
Message-ID: <87tvumrhcb.fsf@fifthhorseman.net> (raw)
In-Reply-To: <20180209204624.GL30368@valgrind.us>

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

On Fri 2018-02-09 12:46:24 -0800, W. Trevor King wrote:
> From later on in PEP 394 [1]:
>
>   It is anticipated that there will eventually come a time where the
>   third party ecosystem surrounding Python 3 is sufficiently mature
>   for this recommendation to be updated to suggest that the python
>   symlink refer to python3 rather than python2.
>
> And from right up at the beginning [2]:
>
>   however, end users should be aware that python refers to python3 on
>   at least Arch Linux (that change is what prompted the creation of
>   this PEP), so python should be used in the shebang line only for
>   scripts that are source compatible with both Python 2 and 3.
>
> On my Gentoo system, I've also selected Python 3 to back ‘python’.  So
> I think your solution should be “add a /usr/bin/python symlink to your
> python3”, not “claim that nmbug is only compatible with Python 3”.

Presumably you still have /usr/bin/python3 in addition to
/usr/bin/python as well.  So the one thing i think we're both agreeing
on is that we use nmbug with python 3.

It looks to me like you're asking me to change my operating system to
accomodate your naming preference.  I'm asking that we put the onus on
developers who really insist on using nmbug with python 2.7 maintain
their own local patch against nmbug, rather than other developers either
modifying their local operating system in potentially disastrous ways
(/usr/bin/python as python3 would cause severe breakage for at least one
python2-only tool i rely on daily, sadly) or carrying their own local
patch against nmbug.  Given that you and i both expect most notmuch
developers to run nmbug against python3 anyway, i can't understand the
allergic reaction to the suggestion that the smaller pool of developers
(those devoted to python2-only systems) be the one to carry the local
patch.

Anyway, I had no idea that this request for something that i think we
fundamentally agree on would cause any controversy, especially given the
expected size and technical sophistication of the nmbug userbase.

i'll drop this request now because i don't understand the origin of the
strength of your reaction, and already wish i'd spent the time i've lost
on it on something more productive :( I hope if you change your mind
you'll come back and recommend it here.

demotivatedly yours,

              --dkg

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

  reply	other threads:[~2018-02-12  5:27 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 [this message]
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=87tvumrhcb.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.org \
    --cc=wking@tremily.us \
    /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).