Re: [ANNOUNCEMENT] Updated: python packages

2021-02-09 Thread Yaakov Selkowitz via Cygwin
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

2021-02-09 Thread Jon Turney

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


Asciidoc failure due to Python versioning

2021-02-09 Thread Adam Dinwoodie
Hi,

As part of the Cygwin Git builds, I've started seeing a failure from AsciiDoc:

ASCIIDOC git-bisect-lk2009.html
  File "/usr/bin/asciidoc", line 101
except KeyError, k: raise AttributeError, k
   ^
SyntaxError: invalid syntax

It looks like the issue is that AsciiDoc requires Python 2, but only
specifies "/usr/bin/env python" in its shebang, and Cygwin Python now
defaults to using Python 3 at that path.

For now I can work around this locally, but I suspect the longer-term
solution will be to update AsciiDoc so it specifies the version of
Python it needs in the shebang. This might already be the case for
upstream AsciiDoc – I've not checked – but I do note AsciiDoc is
currently orphaned; the latest Cygwin version is v8.6.9, released in
2013, whereas the latest version is v9.0.5, released in January 2021.
I'm going to have a quick play to see if it's feasible for me to adopt
the package, but I don't want to make any commitments there; if anyone
else is keen to adopt it, please go ahead!

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