Re: [ITP] python-calver/pretend/pybind11/scikit-build-core/trove-classifiers distros

Jon Turney via Cygwin-apps <[email protected]> Sat, 4 Apr 2026 17:47:04 +0100
Newsgroups gmane.os.cygwin.applications
Message-ID <[email protected]>
On 03/04/2026 23:45, Brian Inglis via Cygwin-apps wrote:
> On 2026-03-31 08:51, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> pretend (https://pypi.org/project/pretend/) is a dependency of 
>> calver's tests, which is a new indirect dependency of a package I 
>> maintain, and as such I'd like to package it for Cygwin.
>> The cygport file for this package is at: https://gitlab.com/hamishmb/ 
>> cygwin- python-pretend
>> pretend is in Debian: https://packages.debian.org/trixie/python3-pretend
>> This, together with some other packages I've submitted ITPs for, will 
>> enable me to release the current version of python-imaging for Python 
>> 3.12 as stable, and start working on wxPython for Python 3.12.
> 
> Hi Hamish,
> 
> Concise distro info summary is available as Repology.org badges:
> 
>      https://repology.org/project/python%3Acalver/badges
>      https://repology.org/project/python%3Apretend/badges
>      https://repology.org/project/python%3Apybind11/badges
>      https://repology.org/project/python%3Ascikit-build/badges
>      https://repology.org/project/python%3Ascikit-build-core/badges
>      https://repology.org/project/python%3Atrove/badges
>      https://repology.org/project/python%3Atrove-classifiers/badges

I've applied a bit of polish to the text under [1], which attempts to 
describe our process for what is "an acceptable package".

I think these package proposals are all already accepted under the 
"requirement of an existing package" rule, but the text there asked 
people to "mention" if the new package is already included in a major 
Linux distribution, rather than clearly stating that is an alternative 
which also makes a package acceptable.

[1] https://cygwin.com/packaging-contributors-guide.html#submitting