public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Adam Dinwoodie <adam@dinwoodie.org>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: python2 removal
Date: Mon, 1 May 2023 18:53:24 +0100	[thread overview]
Message-ID: <88db8aa3-976d-e249-9d22-4bdf6beaeb22@dronecode.org.uk> (raw)
In-Reply-To: <CA+kUOam=qQM2QTtcg1ijdiQbYaf=zY_5a6dGfQnx-kmRCGMRyg@mail.gmail.com>

On 30/04/2023 21:32, Adam Dinwoodie wrote:
> On Sun, 30 Apr 2023 at 19:25, Jon Turney <jon.turney@dronecode.org.uk> wrote:
>>
>> On 25/02/2023 16:51, Adam Dinwoodie via Cygwin-apps wrote:
>>> On Sat, 25 Feb 2023 at 16:23, Jon Turney via Cygwin-apps wrote:
>>>> On 16/01/2023 12:49, Jon Turney via Cygwin-apps wrote:
>>>>> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
>>>>> [...]
>>>>>> Python 2.7 is the last python2 version, which was sunsetted on January
>>>>>> 1, 2020.
>>>>> [...]
>> [...]
>>>>
>>>>    From a brief survey, only offlineimap and urlgrabber (which should
>>>> probably be named python-urlgrabber, since it contains a python module)
>>>> seem to be actively maintained enough to support python3.
>>>>
>>>> So I will probably remove the others, and consider if it's possible and
>>>> worthwhile to update those.
>>>>
>>>> (I also noted that breezy appears to be the python3 replacement for bzr
>>>> and getmail6 appears to be the python3 replacement for getmail.)
>>>
>>> I'm happy to adopt both of these. I'll give Jari a little while to
>>> reclaim them first, not least as I'm not going to have the time to
>>> spend on packaging these for at least a week or so, but if Jari (or
>>> anyone else) doesn't claim them first, I'll send an ITA once I've
>>> checked I can get the packaging to work.
>> Gentle ping to ask if you are still intending to package these?
> 
> Yes, they're both on my to-do list, but I've had a whole bunch of real
> life come up over the past few months. If the delay is causing issues,
> though, I can bump them up my priority list…

That's no problem.  Just checking you hadn't changed your mind :)


  reply	other threads:[~2023-05-01 17:53 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 [this message]
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
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=88db8aa3-976d-e249-9d22-4bdf6beaeb22@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=adam@dinwoodie.org \
    --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).