gobject-introspection 1.86.0-1

[Brian Inglis]

On 2026-03-10 16:28, Jon Turney via Cygwin wrote:
> On 13/09/2025 13:51, Takashi Yano via Cygwin-announce wrote:
>> The following packages have been uploaded to the Cygwin distribution:
>>
>> * gobject-introspection-1.86.0-1
>> * libgirepository1.0_1-1.86.0-1
>> * libgirepository1.0-devel-1.86.0-1
>> * libgirepository1.0-doc-1.86.0-1
>> * girepository-cairo1.0-1.86.0-1
>> * girepository-GIRepository2.0-1.86.0-1
>> * girepository-GLib2.0-1.86.0-1
>> * girepository-x11-1.86.0-1
>>
>> The goal of the project is to describe GObject APIs and collect
>> them in a uniform, machine readable format.
> 
> Hi Takashi,
> 
> I just tripped over a small problem with gobject-introspection:
> 
>> $ /usr/sbin/alternatives --set python3 /usr/bin/python3.12
>>
>> $ g-ir-scanner
>> Traceback (most recent call last):
>>   File "/usr/bin/g-ir-scanner", line 133, in <module>
>>     from giscanner.scannermain import scanner_main
>>   File "/usr/lib/gobject-introspection/giscanner/scannermain.py", line 35, in 
>> <module>
>>     from giscanner.ast import Include, Namespace
>>   File "/usr/lib/gobject-introspection/giscanner/ast.py", line 27, in <module>
>>     from .sourcescanner import CTYPE_TYPEDEF, CSYMBOL_TYPE_TYPEDEF
>>   File "/usr/lib/gobject-introspection/giscanner/sourcescanner.py", line 31, 
>> in <module>
>>     from giscanner._giscanner import SourceScanner as CSourceScanner
>> ModuleNotFoundError: No module named 'giscanner._giscanner'
> 
> This fails because the _giscanner module is built for (and linked against) 
> python3.9.
> 
> 
> I don't quite understand why this is happening since we configure with "- 
> Dpython=${PYTHON3}", so I'd expect end up with the full path to specific python 
> version in the shebang line in g-ir-scanner.
> 
> (I think that's what was happening before upstream switched from autotools to 
> meson)
> 
> In any case, this can be fixed in the cygport by using python3_fix_shebang on 
> this script.

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?
Also about how many updates are actively applied during legacy security support?
Or is my thinking about these releases wrong in some way?

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                 -- Antoine de Saint-Exupéry