public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: Moving from python2 to python3
Date: Sat, 28 Nov 2020 13:11:54 -0500	[thread overview]
Message-ID: <d739f464-b1c7-527d-d84b-cc77b7c1fc3c@cornell.edu> (raw)

This is a followup to a thread with subject "[PATCH] doc: Various fixes to 
makedocbook for python3.8" that began on the newlib list and then moved to

   https://cygwin.com/pipermail/cygwin-apps/2020-August/040442.html,

where it evolved into a discussion of moving from python2 to python3.  A recent 
post on the cygwin list reminded me that we never finished that discussion.  We 
left it with the question of what to do about scripts with a shebang that names 
python but might not work with python3.

With python2 reaching EOL in a month, it seems that we ought to finish that 
discussion and make the move.

Ken

             reply	other threads:[~2020-11-28 18:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-28 18:11 Ken Brown [this message]
2020-12-04 21:04 ` Marco Atzeri
2020-12-29 10:49   ` Marco Atzeri
2020-12-29 12:04     ` Achim Gratz
2020-12-29 13:13       ` Marco Atzeri
2020-12-29 16:42         ` Achim Gratz
2020-12-29 17:02           ` Marco Atzeri
2020-12-29 20:27             ` Marco Atzeri
2020-12-29 20:57               ` Achim Gratz
2020-12-29 21:23                 ` Marco Atzeri
2020-12-30  7:21                   ` Achim Gratz
2020-12-30 11:14                     ` Marco Atzeri
2020-12-30 14:10                       ` ASSI
2020-12-30 15:41                         ` Ken Brown
2020-12-30 18:13                           ` Marco Atzeri
2020-12-29 15:04       ` Ken Brown
2020-12-29 15:46         ` Marco Atzeri

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=d739f464-b1c7-527d-d84b-cc77b7c1fc3c@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).