From: marco atzeri <marco.atzeri@gmail.com>
To: Adam Dinwoodie <adam@dinwoodie.org>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Inconsistent handling of python3-module vs python3x-module packages
Date: Wed, 16 Feb 2022 12:45:58 +0100 [thread overview]
Message-ID: <CAB8Xom-B=w0o3dNTkAOfdeGD_LRaLfte+6hO29gCAuxbw-Qb_w@mail.gmail.com> (raw)
In-Reply-To: <20220216111059.ve7myugtwi7bjggb@lucy.dinwoodie.org>
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 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.
> Adam
Regards
Marco
next prev parent reply other threads:[~2022-02-16 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 11:10 Adam Dinwoodie
2022-02-16 11:45 ` marco atzeri [this message]
2022-02-17 15:42 ` Jon Turney
2022-02-20 16:29 ` Adam Dinwoodie
2022-02-20 17:54 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAB8Xom-B=w0o3dNTkAOfdeGD_LRaLfte+6hO29gCAuxbw-Qb_w@mail.gmail.com' \
--to=marco.atzeri@gmail.com \
--cc=adam@dinwoodie.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).