Unless you are planning to assist with development it should not matter what language an Asciidoc processor is implemented in.
A Python3 Asciidoc was started https://groups.google.com/forum/#!topic/asciidoc/u_Kcg0gUObY but I havn't heard how it is going. For open source software the best incentive you can give is to actually help out. Cheers Lex On 19 November 2015 at 05:50, Craig Luthy <[email protected]> wrote: > Hello, > > I am a Python newby so started out with Python3. Going backwards to Python2 > seems painful. Just wanted to add this as a motivation for porting asciidoc > to Python3. In the meantime I am trying to come up to speed with asciidoctor > instead. > > Thanks, Craig > > On Tuesday, October 16, 2012 at 10:32:56 AM UTC-5, Jens Getreu wrote: >> >> To follow up: >> >> https://groups.google.com/d/topic/asciidoc/0p8l1qD8-40/discussion >> >> here my question concerning python 3: >> When will AsciiDoc be compatible with Python 3? Any plans? >> What is the workload for an experienced programmer? >> >> > -- > You received this message because you are subscribed to the Google Groups > "asciidoc" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/asciidoc. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
