From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH] doc: Various fixes to makedocbook for python3.8
Date: Wed, 26 Aug 2020 11:33:17 -0400 [thread overview]
Message-ID: <88612b10-3bd0-cca0-bf26-4ffca93905ef@cornell.edu> (raw)
In-Reply-To: <427135d6-0d8c-98b9-cfca-7ea2bf400c07@dronecode.org.uk>
On 8/25/2020 11:50 AM, Jon Turney wrote:
> On 24/08/2020 13:58, Ken Brown via Cygwin-apps wrote:
>> On 8/24/2020 6:31 AM, Marco Atzeri via Cygwin-apps wrote:
>>>
>>> Any preference ? For the last option I will use alternatives
>
>> It should default to python3. Fedora performs this via an extra package
>> python-unversioned-command, containing just a symlink /usr/bin/python ->
>> ./python3 as well as a man page symlink /usr/share/man/man1/python.1.gz
>> -> ./python3.1.gz. We could just do the same, no?
>
> Seems like a good idea.
>
>>
>> I think it's time to make python point to python3. I suggest setting
>>
>> /usr/bin/python -> python3
>
> But we'd also need to audit that all packages that containing python scripts
> either:
>
> - use a shebang which names python and work with python3
> - use a shebang which explicitly names python2 or python3
We could start with a HEADSUP to maintainers asking them to check their python
scripts whose shebangs name python. For those scripts whose maintainers don't
respond, we could simply change the scripts to name python2.
Do you have any idea roughly how many scripts we're talking about?
Ken
next prev parent reply other threads:[~2020-08-26 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200822184520.57006-1-jon.turney@dronecode.org.uk>
[not found] ` <ba0fa3cc-e14c-ec8d-38c7-a11ce0ad083c@cornell.edu>
[not found] ` <fe51fc43-007f-1e3a-1eb4-e571ac746fa5@dronecode.org.uk>
[not found] ` <f02d99d6-4338-b8bf-0c0f-7d6259f23cea@SystematicSw.ab.ca>
[not found] ` <20200824100211.GD3272@calimero.vinschen.de>
2020-08-24 10:31 ` Marco Atzeri
2020-08-24 12:58 ` Ken Brown
2020-08-25 15:50 ` Jon Turney
2020-08-26 15:33 ` Ken Brown [this message]
2020-08-24 13:00 ` 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=88612b10-3bd0-cca0-bf26-4ffca93905ef@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/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).