Hi guys,
Thanks for you answers.
On Mon, Oct 8, 2018 at 5:04 AM Ian Jackson
wrote:
> Why would a user want the old python2 asciidoc ? AFAICT from the
> outside of the program the implementation language is a hidden
> detail.
Haha! I've seen people strictly against the upgrade from python 2 to
* Joseph Herlant:
> Hi guys,
>
> As announces a while ago in #895462, the asciidoc package which only
> support python2 is officially EOL.
>
> Notes:
> * The python 2 implementation of asciidoc which, for now, lives at
> https://github.com/asciidoc/asciidoc won't receive any new updates
> * The py
Ian Jackson writes ("Re: Asciidoc transition to the python3 implementation or
just EOL"):
> I know nothing about this. What are the relative advantages and
> disadvantages of asciidoctor vs asciidoc ? Do they process the same
> documents in exactly the same way ?
It occ
On Mon, Oct 08, 2018 at 01:04:52PM +0100, Ian Jackson wrote:
3. have people just move to asciidoctor (it's way more actively
maintained and tested, plus, most package support both nowadays) and
just let the python implementation die naturally
I know nothing about this. What are the relative ad
Joseph Herlant writes ("Asciidoc transition to the python3 implementation or
just EOL"):
> There are currently 2 ways possible to handle the transition:
Follows, 3 ways :-).
Why would a user want the old python2 asciidoc ? AFAICT from the
outside of the program the implementation
Hi guys,
As announces a while ago in #895462, the asciidoc package which only
support python2 is officially EOL.
Notes:
* The python 2 implementation of asciidoc which, for now, lives at
https://github.com/asciidoc/asciidoc won't receive any new updates
* The python 3 implementation that lives at
6 matches
Mail list logo
