From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [patch] cygport : update to python 3.9
Date: Mon, 3 Jan 2022 17:37:37 +0000 [thread overview]
Message-ID: <cfebbf02-4541-b33b-2b11-61ffd5b158c6@dronecode.org.uk> (raw)
In-Reply-To: <9eb22f83-e7e9-1ec5-1aed-5e0b6c8c7848@gmail.com>
On 31/12/2021 10:00, Marco Atzeri wrote:
> Attached patch moves "default" from 3.6 to 3.9
>
> Additional changes:
> Remove 3.5 from all
> Change future to 3.10
>
Thanks.
>
> Other point:
>
> As 3.5 was never really deployed, I think we can remove it from the
> distribution.
>
> As we have a lot of python3-* is obsoleted py python36-*
> what is the best way to updated to python39-* when available ?
Good question. Note the comment before this hunk:
> @@ -128,7 +128,7 @@
> # and MUST NOT be updated when defaults change
> case ${ver} in
> 2.7) declare -g python27_${PYTHON_WHEEL_NAME//[-\.]/_}_OBSOLETES="python-${PYTHON_WHEEL_NAME} python2-${PYTHON_WHEEL_NAME}" ;;
> - 3.6) declare -g python36_${PYTHON_WHEEL_NAME//[-\.]/_}_OBSOLETES="python3-${PYTHON_WHEEL_NAME}" ;;
> + 3.9) declare -g python39_${PYTHON_WHEEL_NAME//[-\.]/_}_OBSOLETES="python3-${PYTHON_WHEEL_NAME}" ;;
> esac
> declare -g python${ver/.}_${PYTHON_WHEEL_NAME//[-\.]/_}_CONTENTS="usr/lib/python${ver}/site-packages/ usr/share/doc/python${ver/.}-${PYTHON_WHEEL_NAME}"
> done
which in full reads:
"
# these were 2&3 at the time of the XY-version split,
# and MUST NOT be updated when defaults change
"
So it seems to me that either that hunk is wrong, or that comment needs
updating.
I'm not sure what the intent is here.
next prev parent reply other threads:[~2022-01-03 17:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 10:00 Marco Atzeri
2022-01-03 17:37 ` Jon Turney [this message]
2022-01-03 21:42 ` Marco Atzeri
2022-05-29 15:54 ` Jon Turney
2022-07-03 12:22 ` Jon Turney
2022-07-03 12:47 ` Marco Atzeri
2022-01-04 16:05 ` Marco Atzeri
2022-01-08 16:32 ` Jon Turney
2022-01-08 17:12 ` Marco Atzeri
2022-06-29 15:36 ` Hamish McIntyre-Bhatty
2022-06-29 15:46 ` Marco Atzeri
2022-06-29 15:51 ` Hamish McIntyre-Bhatty
2022-06-29 18:35 ` Hamish McIntyre-Bhatty
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=cfebbf02-4541-b33b-2b11-61ffd5b158c6@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).