On 02/04/2023 16:47, Jon Turney via Cygwin-apps wrote:
On 14/03/2023 19:17, Jon Turney via Cygwin-apps wrote:
On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
This has come up in discussion a few times, and is now well overdue,
I think.
Python 2.7 is the last python2 version, which was sunsetted on
January 1, 2020.
[...]
3) There might also still be some other packages lurking which just
install a script with a shebang containing 'python', and assume that
python is python2. I don't know how we could identify those.
The remaining cases of packages which have a dependency on python
and/or python2 are either this (packages which contain a python script
with a python shebang line), or the other case which I hadn't
previously considered - a package which contain an executable or
shared library linked with libpython2.7.dll.
So, again I need inspect these to determine what should happen to them.
So here's the list, with *tentative* notes of the disposition for each
package.
As before, I might look at rebuilding some of the more important
packages, as time permits, and some of these are candidates for removal
if not updated, but obviously adoptions and input on what is no longer
useful is welcomed!
So, I think I've more or less come to the end of packages which seems
worthwhile for me to rebuild and/or update.
(There's several things which I haven't updated because their
dependencies also need updating - usually glib, which definitely needs
attending to, but I'm not going to pull on that thread right now...)
I think the next step is to remove the python27 package itself.
This will make it impossible to install anything which requires it on
new installations (existing installations which already have the package
installed will be uneffected).
Once the wailing, rending of garments and gnashing of teeth has died
down, I can remove the python2 modules and bindings at leisure.
Marco,
As python maintainer, any thoughts on when to do this? Anything you want
to get done before that?
