public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
	Jari Aalto <jari.aalto@cante.net>
Subject: Re: python2 removal
Date: Sun, 2 Apr 2023 16:55:03 +0100	[thread overview]
Message-ID: <50a6571c-f6b4-1103-bf5e-80f99ceb2900@dronecode.org.uk> (raw)
In-Reply-To: <01685a2b-5592-971d-fe1c-9cc23c788c92@dronecode.org.uk>

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.
[...]
	
> source package         package                 maintainer                    notes      
> 
> cfv                    cfv                     Jari Aalto                    [†][§]
> svn-load               svn-load                Jari Aalto                    [†][§]
> webcheck               webcheck                Jari Aalto                    [†][§]
> 
> [†] contains some python scripts
> [§] script is python2 only, not compatible with python3

Hi Jari,

I believe these packages all need updating for python3.

Please confirm if this assessment is correct, and let me know if you 
intend to do this, otherwise I will assume these packages are orphaned 
and they will be removed.

Thanks.


  reply	other threads:[~2023-04-02 15:55 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15 12:52 Jon Turney
2023-01-15 19:31 ` Ken Brown
2023-01-16 12:49   ` Jon Turney
2023-01-16 14:22     ` Ken Brown
2023-01-16 12:49 ` Jon Turney
2023-02-25 16:23   ` Jon Turney
2023-02-25 16:51     ` Adam Dinwoodie
2023-02-26 11:56       ` Jon Turney
2023-04-30 18:25       ` Jon Turney
2023-04-30 20:32         ` Adam Dinwoodie
2023-05-01 17:53           ` Jon Turney
2023-02-25 16:23   ` Jon Turney
     [not found]     ` <003a01d94a86$750f4b70$5f2de250$@samsung.com>
2023-02-27 13:36       ` Jon Turney
2023-02-25 16:23   ` Jon Turney
2023-03-07 17:27   ` Jon Turney
2023-01-17  2:27 ` David Rothenberger
2023-03-14 19:16 ` Jon Turney
2023-03-14 19:17 ` Jon Turney
2023-03-15 12:56   ` Brian Inglis
2023-03-15 16:46     ` marco atzeri
2023-03-16 13:29     ` ITA (was Re: python2 removal) Jon Turney
2023-03-16 15:53       ` ITA xlsx2csv " Brian Inglis
2023-03-16 18:57         ` Jon Turney
2023-03-16 21:12           ` Brian Inglis
2023-03-22  7:36           ` Jari Aalto
2023-03-22 16:23             ` Jon Turney
2023-04-02 15:47   ` python2 removal Jon Turney
2023-04-02 15:55     ` Jon Turney [this message]
2023-06-01 16:54       ` Jon Turney
2023-04-02 16:00     ` Jon Turney
2023-04-03  1:08     ` marco atzeri
2023-04-11  6:49       ` Marco Atzeri
2023-06-04 19:17     ` Jon Turney
2023-07-02 14:30       ` Jon Turney
2023-07-07 18:54         ` Marco Atzeri
2023-07-09 16:50           ` Jon Turney
2024-01-18 19:31             ` Jon Turney
2024-01-18 19:40               ` Jon Turney
2024-01-19 18:23                 ` Hamish McIntyre-Bhatty
2024-04-10 19:19                   ` Hamish McIntyre-Bhatty
2024-04-11 12:23                     ` Jon Turney
2023-06-11 18:06     ` Jon Turney

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=50a6571c-f6b4-1103-bf5e-80f99ceb2900@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=jari.aalto@cante.net \
    /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).