From: Jon Turney <jon.turney@dronecode.org.uk>
To: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: Re: [PATCH] doc: Various fixes to makedocbook for python3.8
Date: Sun, 23 Aug 2020 20:41:30 +0100 [thread overview]
Message-ID: <fe51fc43-007f-1e3a-1eb4-e571ac746fa5@dronecode.org.uk> (raw)
In-Reply-To: <ba0fa3cc-e14c-ec8d-38c7-a11ce0ad083c@cornell.edu>
On 23/08/2020 16:23, Ken Brown wrote:
> On 8/22/2020 2:45 PM, Jon Turney wrote:
>> ---
>> newlib/doc/makedocbook.py | 8 +++++---
>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/newlib/doc/makedocbook.py b/newlib/doc/makedocbook.py
>> index 92d0f279d..3fab26f1a 100755
>> --- a/newlib/doc/makedocbook.py
>> +++ b/newlib/doc/makedocbook.py
[...]
> Would it make sense to also change the shebang line so that
> makedocbook.py uses python3? Currently the build of Cygwin on Fedora
> uses python3, but the build of Cygwin on Cygwin uses python2. This is
> of no great importance, but a recent IRC discussion shows that it can be
> confusing.
Yeah, I guess that would make some sense, given that python2 is now EOL.
Otoh, making it gratuitously not work with python2 seems a bit harsh.
On the gripping hand, reading PEP 0394, I see it doesn't actually
require that 'python' exist at all, so I guess changing the shebang as
you suggest is the right thing to do.
next prev parent reply other threads:[~2020-08-23 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 18:45 Jon Turney
2020-08-23 15:23 ` Ken Brown
2020-08-23 19:41 ` Jon Turney [this message]
2020-08-23 22:49 ` Brian Inglis
2020-08-24 10:02 ` Corinna Vinschen
2020-08-24 10:01 ` Corinna Vinschen
2020-08-25 19:45 ` Jon Turney
2020-08-26 7:50 ` Corinna Vinschen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe51fc43-007f-1e3a-1eb4-e571ac746fa5@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=newlib@sourceware.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.
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).