Re: gobject-introspection 1.86.0-1

On 11/03/2026 14:38, Brian Inglis via Cygwin wrote:
[...]
> Looking at release and useful bugfix support dates in:
> 
>      https://devguide.python.org/versions/
> 
> We are still on Python 3.9 which went EoL last October, so with Python 
> 3.13 bugfix support ending this October, and each release until 3.16 
> each following October until 2029 (presumably Python 3 Eol?)/
> Should we be trying to get updated more frequently, like maybe even 
> releases every two years, while they still have bugfix support, and have 
> mot dropped to security fixes only?

This is a "could things be better" question.  The answer is obviously 
yes, but how to make it happen is less clear.

I guess I'm going to defer to Marco, who's been grinding through the 
necessary work to get us onto python 3.12. Maybe he has some ideas about 
what kind of assistance or automation might help?


> Also about how many updates are actively applied during legacy security 
> support?
> Or is my thinking about these releases wrong in some way?

(I think in this specific case, where g-ir-scanner is a python script 
installed in /usr/bin, which imports a C language python module 
installed in /usr/lib/gobject-introspection/giscanner, but *linked* 
against a specific version of the python runtime, the actual python 
version used is secondary to the concern that the shebang in the script 
must match that version, otherwise running the command line tool fails...)


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple