Stargazer,
Have you tried the Python 3 port at asciidoc/asciidoc-py3, its
intended to be compatible (as possible), so your tooling will keep
working?
Cheers
Lex
On Thu, 14 Jun 2018 at 14:21, Stargazer wrote:
>
> Tried AsciiDoctor awhile back. We prefer Python 3, rather than Ruby. There
> were
Tried AsciiDoctor awhile back. We prefer Python 3, rather than Ruby. There
were some issues that we would have to address that would require changes
to our doc,
config files, and/or procedures.
Thanks for all the updates.
> Really like Asciidoc and recommend it all the time.
>
> Good to
> The largest change in Python 3 is handling of strings. The amount of work
> to port asciidoc using Python 2 to asciidoc3 using Python 3 must have been
> significant.
>
>
> Hi stargazer,
yes in deed: the pitfalls of migrating Python2 to Python3 str/unicode was
probably the most annoying and
On Fri, 8 Jun 2018 at 15:05, Stargazer wrote:
>
> Interesting read. I hope it gets ironed out as needed. I thought asciidoc
> written in Python 2 was going to age away. The official upgrade path from
> Python 2.7 is to Python 3 (PEP 404). The EOL for Python 2.7 is 2020 (PEP 373).
The EOL is
Interesting read. I hope it gets ironed out as needed. I thought asciidoc
written in Python 2 was going to age away. The official upgrade path from
Python 2.7 is to Python 3 (PEP 404). The EOL for Python 2.7 is 2020 (PEP
373).
The largest change in Python 3 is handling of strings. The amount
On Thu, 7 Jun 2018 at 08:10, Stargazer wrote:
>
> Ok. Thanks Lex.
>
> It appears Berthold has things well under control regarding licensing
> @https://asciidoc3.org/blog/.
Still a work in progress, See the thread at
https://github.com/asciidoc3/asciidoc3/issues/1
It should be noted that this
Stargazer, there is also a Python 3 port at asciidoc/asciidoc-py3 you
could try that does not have that problem.
Regards
Lex
On Thu, 7 Jun 2018 at 07:26, Dan Allen wrote:
>
> > Maybe we can get a write-up in the Linux Pro Magazine.
>
> I would hold off on that as there is currently an unresolved
> Maybe we can get a write-up in the Linux Pro Magazine.
I would hold off on that as there is currently an unresolved copyright /
license dispute with this fork.
-Dan
On Wed, Jun 6, 2018 at 3:23 PM, Stargazer
wrote:
> Just came across this entry. Downloaded the tar.gz from
>
On Wed, Apr 18, 2018 at 12:28:14PM +0100, Derek Jones wrote:
> Dan,
>
> How many other people have jumped to the same conclusion that
> I did?
>
> Why not point the news page at the Github release blog?
>
Hi devs,
sorry for the intrusion...
Why not DIY?
Dan,
How many other people have jumped to the same conclusion that
I did?
Why not point the news page at the Github release blog?
You have a point that the news section of the website has not mentioned any
new releases. We decided not to use that to announce release anymore
because it was too
Derek,
You have a point that the news section of the website has not mentioned any
new releases. We decided not to use that to announce release anymore
because it was too much overhead. All the releases are announced instead on
the GitHub releases page, which I'm using as the release blog.
On 18 April 2018 at 09:52, Derek Jones wrote:
> Dan,
>
>> https://rubygems.org/gems/asciidoctor/versions
>
>
> Thanks for this.
>
>> Please research more before commenting about the health of a project. It's
>> very damaging to the project to make such impulsive statements.
>
Derek,
You are clearly looking in the wrong place. Asciidoctor has incredibly high
activity on both code and documentation.
https://github.com/asciidoctor/asciidoctor
https://github.com/asciidoctor/asciidoctor/issues?q=is%3Aissue+sort%3Aupdated-desc+is%3Aclosed
On 18 April 2018 at 08:05, Derek Jones wrote:
> Lex,
>
>> What is your basis for that statement? I am not an Asciidoctor dev,
>> but I can say it most definitely does not seem to have stalled to me. >
>> Have you been watching the Github repository?
>
>
> The last update
Lex,
What is your basis for that statement? I am not an Asciidoctor dev,
but I can say it most definitely does not seem to have stalled to me. > Have
you been watching the Github repository?
The last update listed on the asciidoctor website is from a few years
ago.
There were 21 code
On 17 April 2018 at 21:35, Derek Jones wrote:
>
>> you can find the brand-new Python3 port AsciiDoc3 at www.asciidoc3.org and
>> on github.com/asciidoc3/asciidoc3.
>> All 170 AsciiDoc testcases are passed! Have fun with 'Text based document
>> generation using Python 3.x'.
>
>
you can find the brand-new Python3 port AsciiDoc3 at www.asciidoc3.org and
on github.com/asciidoc3/asciidoc3.
All 170 AsciiDoc testcases are passed! Have fun with 'Text based document
generation using Python 3.x'.
It's great to see development happening (asciidoctor work seems t
have
Congratulations on getting this working. Given how many attempts fell
short, that really speaks volumes to what a notable accomplishment this is.
I do wish you had consulted with the project before selecting the domain
name. (If you did, and I missed it, I apologize for suggesting you didn't).
My
Hi,
Neat, well done.
Cheers
Lex
On 17 April 2018 at 08:59, wrote:
> Hi all,
> you can find the brand-new Python3 port AsciiDoc3 at www.asciidoc3.org and
> on github.com/asciidoc3/asciidoc3.
> All 170 AsciiDoc testcases are passed! Have fun with 'Text based document
>
19 matches
Mail list logo