From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: [patch] cygport : update to python 3.9
Date: Fri, 31 Dec 2021 11:00:24 +0100 [thread overview]
Message-ID: <9eb22f83-e7e9-1ec5-1aed-5e0b6c8c7848@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
Attached patch moves "default" from 3.6 to 3.9
Additional changes:
Remove 3.5 from all
Change future to 3.10
Other point:
As 3.5 was never reall deployed, I think we can remove it from the
distibution.
As we have a lot of python3-* is obsoleded py python36-*
what is the best way to updated to python39-* when available ?
Regards
Marco
[-- Attachment #2: cygport-python3.patch --]
[-- Type: text/plain, Size: 2488 bytes --]
--- python-wheel.cygclass-bk 2021-12-31 08:53:33.186729100 +0100
+++ python-wheel.cygclass 2021-12-31 10:10:42.372875400 +0100
@@ -60,12 +60,12 @@
# inherit python-wheel
# DESCRIPTION
# A colon-seperated list of version(s) for which this module should be built.
-# Some aliases are also accepted:
-# * all: all supported 3.y versions (currently: 3.5 through 3.8)
-# * future: the default and upcoming 3.y versions (currently: 3.7, 3.8)
-# * default: the default 3.y version(s) (currently: 3.7, 3.8)
+# Some aliases are also accepted (at 2021 Dec 31st):
+# * all: all supported 3.y versions (currently: 3.6 through 3.9)
+# * future: the default and upcoming 3.y versions (currently: 3.9, 3.10)
+# * default: the default 3.y version(s) (currently: 3.8, 3.9)
# * 2: the default 2.x version (permanently 2.7)
-# * 3: the default 3.x version (currently: 3.8)
+# * 3: the default 3.x version (currently: 3.9)
# This variable must be defined before inheriting python-wheel.cygclass.
# If undefined, "default" is assumed.
# NOTES
@@ -93,11 +93,11 @@
for ver in ${PYTHON_WHEEL_VERSIONS//:/ }
do
case "${ver}" in
- all) _tmp_wheel_v+=3.5:3.6:3.7:3.8: ;;
- future) _tmp_wheel_v+=3.7:3.8: ;;
- default) _tmp_wheel_v+=3.7:3.8: ;;
+ all) _tmp_wheel_v+=3.6:3.7:3.8:3.9: ;;
+ future) _tmp_wheel_v+=3.9:3.10: ;;
+ default) _tmp_wheel_v+=3.8:3.9: ;;
2) _tmp_wheel_v+=2.7: ;;
- 3) _tmp_wheel_v+=3.8: ;;
+ 3) _tmp_wheel_v+=3.9: ;;
*) _tmp_wheel_v+=$ver: ;;
esac
done
@@ -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
@@ -195,7 +195,7 @@
# ENSUREPIP_OPTIONS=install: pipX, pipX.Y, easy_install-X.Y
case ${ver} in
- 2.7|3.8) export ENSUREPIP_OPTIONS="install" ;;
+ 2.7|3.9) export ENSUREPIP_OPTIONS="install" ;;
*) export ENSUREPIP_OPTIONS="altinstall" ;;
esac
pip${ver} install -I dist/${whl} --root ${D} --prefix /usr --no-compile --no-deps --no-warn-script-location || error "pip${ver} install failed"
next reply other threads:[~2021-12-31 10:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 10:00 Marco Atzeri [this message]
2022-01-03 17:37 ` Jon Turney
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=9eb22f83-e7e9-1ec5-1aed-5e0b6c8c7848@gmail.com \
--to=marco.atzeri@gmail.com \
--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).