Re: Python 3.5 and 3.6 removal (was Re: Bonfire of the Packages)

[Jon Turney <jon.turney@dronecode.org.uk>]

On 27/03/2024 21:18, Brian Inglis via Cygwin-apps wrote:
> On 2024-03-27 14:07, Jon Turney via Cygwin-apps wrote:
>> On 24/03/2024 18:51, Brian Inglis via Cygwin-apps wrote:
>>> On 2024-03-24 11:46, Jon Turney via Cygwin-apps wrote:
>>>> On 24/03/2024 17:31, Marco Atzeri via Cygwin-apps wrote:
>>>>> On 24/03/2024 15:07, Jon Turney wrote:
>>>>>> On 24/09/2023 13:32, Jon Turney via Cygwin-apps wrote:
[...]
>>
>> Are they supposed to migrate to some alternate bindings maybe 
>> available from a separate repo? Or are they just out of luck?
> 
> SOL! Dropped them in 1.52, probably why 1.31.0..1.51.0 are hanging around.

Nice :S

>>> Feel free to purge as appropriate, or tell me what to add to cygport, 
>>> hints, etc!
>>
>> So, the long list of source versions will hopefully be reduced in the 
>> fullness of time...
> 
> Could I just add to nghttp2.cygport that nghttp2 obsoletes 
> python{2{,7},3{,6,7,8,9}}-nghttp2?
> Does this have to remain in the cygport forever to avoid keeping nghttp2 
> vx.x.x around?

You could, but that's probably not the correct thing to do unless you 
really, really want to forcibly uninstall those packages for anyone who 
has installed them, which seems like unnecessary breakage.

I don't think you have to do anything.  There's nothing "wrong" here.

If it really offends your sense of aesthetics, I suggest you just expire 
some subset of the old versions using the vault command [1].

[1] https://cygwin.com/package-upload.html#deleting