Re: [ANNOUNCEMENT] Updated: python packages
On 07/03/2021 20:44, Ken Brown via Cygwin wrote: On 3/7/2021 2:34 PM, Marco Atzeri via Cygwin wrote: On 07.03.2021 17:58, Ken Brown via Cygwin wrote: 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)? the issue is that Cygport creates the "obsolete" python3-foo that is replaced by python36-foo automatically. we should change cygport to use python38 instead --- $ cat python3-lxml/python3-lxml-4.6.2-1.hint category: _obsolete requires: python36-lxml sdesc: "Obsoleted by python36-lxml" ldesc: "The python3-lxml package is obsolete. Selecting this package for installation will cause the python36-lxml package, which replaces this one, to be installed instead." external-source: python-lxml --- As long as you have to patch cygport anyway, maybe it would be better to have cygport create an empty (but not obsolete) package. I think users might find it confusing that they have to install an obsolete package to get what they want. Also, obsolete packages are normally hidden in the setup UI. Yeah. I've wanted to improve how things in this area for a while (since there are some checks which calm does for 'should this package be obsolete') which are thwarted by this kind of package. So, I've added 'Virtual' to the list of package categories that calm permits, if you want to use it for this kind of meta-package. -- 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
Re: [ANNOUNCEMENT] Updated: python packages
On 2021-03-07 13:44, Ken Brown via Cygwin wrote: On 3/7/2021 2:34 PM, Marco Atzeri via Cygwin wrote: On 07.03.2021 17:58, Ken Brown via Cygwin wrote: 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)? the issue is that Cygport creates the "obsolete" python3-foo that is replaced by python36-foo automatically. we should change cygport to use python38 instead --- $ cat python3-lxml/python3-lxml-4.6.2-1.hint category: _obsolete requires: python36-lxml sdesc: "Obsoleted by python36-lxml" ldesc: "The python3-lxml package is obsolete. Selecting this package for installation will cause the python36-lxml package, which replaces this one, to be installed instead." external-source: python-lxml As long as you have to patch cygport anyway, maybe it would be better to have cygport create an empty (but not obsolete) package. I think users might find it confusing that they have to install an obsolete package to get what they want. Also, obsolete packages are normally hidden in the setup UI. Hidden generic/virtual package selections in Debian apt/-get and other package managers are annoying as users (I!) don't know how to do anything when they find out about them e.g. $ apt show exim Package: exim State: not a real package (virtual) N: Can't select candidate version from package exim as it has no candidate N: Can't select versions from package 'exim' as it is purely virtual N: No packages found Suggest adding a category like ~Generic or ~Virtual to sort out of the way but be selectable if you search for Python, Perl, Ruby, etc. I have been unable to find any definitive category list where that might be checked, except in cygwin-apps/calm/genini, and I believe that is not being used any more, as it is missing Debug but includes obsolete Mingw. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] -- 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
Re: [ANNOUNCEMENT] Updated: python packages
On 3/7/2021 2:34 PM, Marco Atzeri via Cygwin wrote: On 07.03.2021 17:58, Ken Brown via Cygwin wrote: 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 the issue is that Cygport creates the "obsolete" python3-foo that is replaced by python36-foo automatically. we should change cygport to use python38 instead --- $ cat python3-lxml/python3-lxml-4.6.2-1.hint category: _obsolete requires: python36-lxml sdesc: "Obsoleted by python36-lxml" ldesc: "The python3-lxml package is obsolete. Selecting this package for installation will cause the python36-lxml package, which replaces this one, to be installed instead." external-source: python-lxml --- As long as you have to patch cygport anyway, maybe it would be better to have cygport create an empty (but not obsolete) package. I think users might find it confusing that they have to install an obsolete package to get what they want. Also, obsolete packages are normally hidden in the setup UI. 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
Re: [ANNOUNCEMENT] Updated: python packages
On 07.03.2021 17:58, Ken Brown via Cygwin wrote: 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 the issue is that Cygport creates the "obsolete" python3-foo that is replaced by python36-foo automatically. we should change cygport to use python38 instead --- $ cat python3-lxml/python3-lxml-4.6.2-1.hint category: _obsolete requires: python36-lxml sdesc: "Obsoleted by python36-lxml" ldesc: "The python3-lxml package is obsolete. Selecting this package for installation will cause the python36-lxml package, which replaces this one, to be installed instead." external-source: python-lxml --- -- 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
Re: [ANNOUNCEMENT] Updated: python packages
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 +, 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
Re: [ANNOUNCEMENT] Updated: python packages
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 +, 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.
there is a bit of cleaning to do on the python3-* tree and package pull,
but first we need to patch cygport to stop creating additional
python3-* packages if not requested.
I guess after the Perl 5.32 I could look on it
as spring project.
--
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
Re: [ANNOUNCEMENT] Updated: python packages
On 10.02.2021 03:29, Yaakov Selkowitz via Cygwin wrote:
On Tue, 2021-02-09 at 21:31 +, 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.
there is a bit of cleaning to do on the python3-* tree and package pull,
but first we need to patch cygport to stop creating additional
python3-* packages if not requested.
I guess after the Perl 5.32 I could look on it
as spring project.
Regards
Marco
--
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
Re: [ANNOUNCEMENT] Updated: python packages
On Tue, 2021-02-09 at 21:31 +, 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.
>
> 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.
--
Yaakov
--
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
Re: [ANNOUNCEMENT] Updated: python packages
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.
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).
--
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
Re: [ANNOUNCEMENT] Updated: python packages
On 1/22/2021 4:37 PM, Marco Atzeri via Cygwin-announce via Cygwin wrote: Several python packages have been promoted from test to stable Thank you, Marco! 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
