On 3/7/2021 10:37 AM, Jon Turney wrote:
On 10/02/2021 08:19, Marco Atzeri via Cygwin wrote:
On 10.02.2021 03:29, Yaakov Selkowitz via Cygwin wrote:
On Tue, 2021-02-09 at 21:31 +0000, Jon Turney wrote:
On 22/01/2021 21:37, Marco Atzeri via Cygwin-announce via Cygwin wrote:
Several python packages have been promoted from test to stable
[...]
python{36,37,38}-lxml-4.6.2-1
Marco,
I noticed something a bit odd, which I'm not sure is expected or not.
expected :-(
Not time in the past to work on it.
I was focusing on deploying python38-* as first priority
If I install 'python3-lxml', I get 'python36-lxml', which doesn't do me
much good with 'python3' installed (which gets me python3.8 currently).
When I changed the packaging scheme from pythonX-* to pythonXY-*, 3.6 was the
"3" version at the time, and the python3-* created alongside python36-* were
only meant to be upgrade helpers from that point forward.
Ok. I'm not sure 'python3-foo' just as an upgrade helper is ideal.
Let me explain my use case:
I have a CI job which runs 'setup -q -P python3,python3-lxml'. It's nice if
that gets me something where "python3 -c 'import lxml'" works, and doesn't
require changing every time the default python version is updated.
Currently python3 is a meta-package whose main purpose is to require the default
python version (currently python38). Marco, couldn't you just make python3-foo
a meta-package that requires the corresponding python*-foo (currently python38-foo)?
Ken
--
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
