Re: Adjusting cygport's default PYTHON_WHEEL_VERSIONS

Marco Atzeri via Cygwin-apps <[email protected]> Tue, 16 Dec 2025 19:31:23 +0100
Newsgroups gmane.os.cygwin.applications
Message-ID <[email protected]>
On 16/12/2025 00:57, Jon Turney wrote:
> 
> Hi Marco,
> 
> I am planning on adjusting the default for PYTHON_WHEEL_VERSIONS from 
> "3.8:3.9" to "3.9:3.12" in an upcoming cygport release.

Thanks.
I will try to expand 3.12 package coverage as much as possible and start 
the 3.13 series.
The lack of released rust compiler is the major blocking point for
the cryptographic modules.

> I also learnt something while looking into making this change which I'll 
> try to document more clearly in the manual:
> 
> The python3-wheel cygclass is just a thin wrapper around the python- 
> wheel cygclass, which sets PYTHON_WHEEL_VERSIONS=${PYTHON3_VERSION} 
> (i.e. it only ever builds for the current python version).
> 
> So, generally, all python modules should be using python-wheel.

I will check what I am using between python3-wheel and python-wheel
I remember some packages have issues, but I do not remember the exact 
details.

> I also noticed one other place where the "default version" of python is 
> significant:
> 
> https://cygwin.com/cgit/cygwin-apps/cygport/tree/cygclass/python- 
> wheel.cygclass#n209
> 
> I wonder if this should just be using "ENSUREPIP_OPTIONS=altinstall" for 
> all versions, and then those alternate names are controlled by 
> alternatives after package install? (I guess you're doing something to 
> arrange that at present?)
> 
> (which has the advantage that it doesn't bake those names into the 
> package, so they can be taken over by a later version easily)

I am not doing anything on the matter, but it could be the source of 
some problems mentioned  in the area ; need to check.

Regards
Marco