X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org 317DB3858D20
Authentication-Results:	sourceware.org; dmarc=none (p=none dis=none)
	header.from=dronecode.org.uk
Authentication-Results:	sourceware.org; spf=none smtp.mailfrom=dronecode.org.uk
Authentication-Results:	btinternet.com;
	auth=pass (PLAIN) smtp.auth=jonturney AT btinternet DOT com;
	bimi=skipped
X-SNCR-Rigid:	613A912414FC1138
X-Originating-IP:	[86.139.167.74]
X-OWM-Source-IP:	86.139.167.74 (GB)
X-OWM-Env-Sender:	jonturney AT btinternet DOT com
X-VadeSecure-score:	verdict=clean score=0/300, class=clean
X-RazorGate-Vade:	gggruggvucftvghtrhhoucdtuddrgedvvddrjeekgdejkecutefuodetggdotefrodftvfcurfhrohhfihhlvgemuceutffkvffkuffjvffgnffgvefqofdpqfgfvfenuceurghilhhouhhtmecufedtudenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepkfffgggfuffvfhfhjggtgfesthejredttdefjeenucfhrhhomheplfhonhcuvfhurhhnvgihuceojhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukheqnecuggftrfgrthhtvghrnhepffekiefgudejheetudeigfejledtleegleetkeduteeftdfffefhueefgfeutedtnecukfhppeekiedrudefledrudeijedrjeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurddutdefngdpihhnvghtpeekiedrudefledrudeijedrjeegpdhmrghilhhfrhhomhepjhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukhdpnhgspghrtghpthhtohepuddprhgtphhtthhopegthihgfihinhestgihghifihhnrdgtohhm
X-RazorGate-Vade-Verdict:	clean 0
X-RazorGate-Vade-Classification:	clean
Message-ID:	<ccd673f4-b835-b27b-cfae-2ac865cbe003@dronecode.org.uk>
Date:	Thu, 17 Feb 2022 15:42:56 +0000
MIME-Version:	1.0
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
	Thunderbird/91.6.0
Subject:	Re: Inconsistent handling of python3-module vs python3x-module
	packages
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
References:	<20220216111059 DOT ve7myugtwi7bjggb AT lucy DOT dinwoodie DOT org>
	<CAB8Xom-B=w0o3dNTkAOfdeGD_LRaLfte+6hO29gCAuxbw-Qb_w AT mail DOT gmail DOT com>
From:	Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
In-Reply-To:	<CAB8Xom-B=w0o3dNTkAOfdeGD_LRaLfte+6hO29gCAuxbw-Qb_w@mail.gmail.com>
X-Spam-Status:	No, score=-3570.8 required=5.0 tests=BAYES_00, FORGED_SPF_HELO,
	KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
	SPF_HELO_PASS, SPF_NONE, TXREP,
	T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4
X-Spam-Checker-Version:	SpamAssassin 3.4.4 (2020-01-24) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On 16/02/2022 11:45, marco atzeri wrote:
> On Wed, Feb 16, 2022 at 12:11 PM Adam Dinwoodie  wrote:
>>
>> While wrangling a bunch of Python packages for my Cygwin installation,
>> I've noticed an inconsistency about how python3 vs python3x packages are
>> installed.
> 
> Only one ? ;-)
> 
>> As an example: the python3 package itself describes itself as a
>> meta-package; the package itself is almost empty, and the key thing
>> selecting the package does is depend on the latest python3x package,
>> currently python39.  The same behaviour is in place with, for example,
>> python3-tkinter.
> 
> Yes, these are real meta packages that pull the latest version
> 
>> However the python3-pytest package is marked as obsolete, and is
>> obsoleted by python36-pytest.  If I select python3-pytest for
>> installation, the package that's actually installed is python36-pytest,
>> even though there's a python39-pytest package available.
>>
>> This inconsistency means that someone naively installing python3-tkinter
>> and python3-pytest will end up with both python3.9 and python3.6
>> installed, with neither installation having access to both the pytest
>> and tkinter modules.
> 
> This is an artifact of of cygport creating python3-xxxx packages
> also for packages that never had a real package called like that.
> We had  a discussion if it was worth to make the  python3-xxxx pulling the
>   python39-xxxx instead of python39-xxxx and it was decided against it.

I think this is more the emergent behaviour due to various changes than 
the result of a considered decision.

>> I think this inconsistency is liable to cause confusion; it certainly
>> confused me until I worked out what was going on.  In my ideal world,
>> we'd be in a situation where I could specify `python3-foo` to an install
>> script and it'd automatically pick up the latest Python version
>> available; I could specify `python3x-foo` if I wanted a specific older
>> release.  But at the very least, I'd really like to see these packages
>> being handled consistently one way or another.
> 
> I expect no one looking for a package will look for obsolete packages.

It makes 'install python3-foo' a moving target for scripts.

Patches to cygport to make this work better welcome!

-- 
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

- Raw text -