From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [patch] cygport : update to python 3.9
Date: Sun, 3 Jul 2022 14:47:04 +0200 [thread overview]
Message-ID: <6e97ac7c-2a6b-d714-96ea-346039683a71@gmail.com> (raw)
In-Reply-To: <726f1956-fecc-bd27-f4ff-03aeb34eb286@dronecode.org.uk>
On 03.07.2022 14:22, Jon Turney wrote:
> On 29/05/2022 16:54, Jon Turney wrote:
>>>
>>> Following is a sort of RFC, so let me know your opinion.
>>>
>>> Currently we have two type of Python packages
>>>
>>> 1) Pure python that exists at max as 2.7 3.6 3.7 3.8 3.9 plus 2 and 3
>>>
>>> in that case 2/2.7 3/3.6 are EOL;
>>> I stopped last year to update the 2.7 and I am thinking to do the
>>> same for 3.6 now.
>>>
>>> I do not see the need to continue to update 3.7, it never become
>>> default as we jumped from 3.6 to 3.8 and it is not more
>>> active upstream:
>>> https://www.python.org/dev/peps/pep-0537/#lifespan
>>>
>>> We can update the 3.8 and 3.9 while preparing/testing for 3.10
>>>
>>> source package will continue to use the "python-*" form, while
>>> "python3-*" should not be used.
>>
>> I disagree about the second half of that sentence.
>>
>> From a package management point of view:
>>
>> * being able to script 'install python3, python3-foo' and get the foo
>> for the default python is useful
>>
>> * having the setup remember that python3-foo was installed (causing
>> python39-foo to be installed), means when the default python is
>> updated from python39 to python3nn, setup will also install
>> python3nn-foo, so local scripts with a python3 shebang which 'import
>> foo' continue to work.
>>
>> I've posted a cygport patch which adjusts cygport to generate these
>> python3-foo virtual packages. What do you think about that?
>
> I've released a cygport 0.35.2 with that patch [1] applied.
>
> Please let me know if it causes you problems.
>
> (It also fixes an issue where the presence of a python3 shebang wasn't
> correctly detected as a dependency on the python3 package due to python3
> being a symlink now)
>
> [1] https://cygwin.com/pipermail/cygwin-apps/2022-May/042051.html
>
Thanks Jon
appreciated.
I will start to refresh python packages,
as soon I finish the current run to update some of the other stuff
that I left behind in the first half of the year.
Regards
Marco
next prev parent reply other threads:[~2022-07-03 12:47 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
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 [this message]
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=6e97ac7c-2a6b-d714-96ea-346039683a71@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).