On Sunday, May 22, 2016 at 1:11:47 AM UTC-7, Lex Trotman wrote: This is probably part of the reason why its embedded in the backends, > no install issues. > > Why not put it in the same place as the asciidoc config, thats a > prefix that asciidoc knows and you should be able to add it in front > of the filename to make it an absolute pathname. >
Like this? - https://github.com/ShadowKyogre/asciidoc/commit/25445945343da9fc87d59a64e1598e579fcc6eb0 I would have said don't worry about Python 2.6, if you look at the > Travis results you will see that current asciidoc apparently contains > syntax (in a filter) that breaks 2.6. My understanding was that > support for old versions of Python 2 were for Jython, but it now > supports 2.7 so it should be ok. > > I can't test, but if it passes the regression tests thats a good start. > Well, that's good to know! At least I don't have to worry about finding bugs for an older version. When you think its ready we should make a repository for it under the > asciidoc organisation so it can get wider visibility and be available > for distros to package. > All right! That being said, if it's going to be in a separate repo, should I remove the original python2 versions in the development repo? -- 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 https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
