public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: newlib@sourceware.org
Subject: Re: [PATCH] doc: Various fixes to makedocbook for python3.8
Date: Sun, 23 Aug 2020 16:49:25 -0600	[thread overview]
Message-ID: <f02d99d6-4338-b8bf-0c0f-7d6259f23cea@SystematicSw.ab.ca> (raw)
In-Reply-To: <fe51fc43-007f-1e3a-1eb4-e571ac746fa5@dronecode.org.uk>

On 2020-08-23 13:41, Jon Turney wrote:
> 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.

Is it not perhaps time to switch python from EOL python2 to python3, as there
are only 183 python2, 125 python27 to 199 python3, 129 python37 packages.

We are deemphasising Cygwin 32 and no longer promote it as equal to Cygwin 64,
but are far from calling it EOL, whereas not even security or severe bug fixes
will be considered, never mind distributed, for python2: its death was announced
10 years ago, confirmed 5 years ago, complete 4 months ago, it is now static and
potentially unsafe at 2.7.18, and its estimate of Napier's constant e is as
accurate as it will ever get! ;^>

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]

  reply	other threads:[~2020-08-23 22:49 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
2020-08-23 22:49     ` Brian Inglis [this message]
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=f02d99d6-4338-b8bf-0c0f-7d6259f23cea@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).