On 03/01/13 11:56, Lex Trotman wrote: > On 2 January 2013 23:20, Jens Getreu <[email protected]> wrote: >> Am Mittwoch, 2. Januar 2013 01:32:49 UTC+2 schrieb Lex Trotman: >>> >>> On 1 January 2013 20:20, Stuart Rackham <[email protected]> wrote: >>> >>>> this path than me. My problem with the Python 3 thing is that I can't >>>> think of a single reason I (emphasis on "I") would want to other than >>>> "gee, that would be nice", so I'm not planning to roll my sleeves up any >>>> time soon on this one. >>> >> >> Hi Stuart and Lex, >> >> short term python 3 migration seems crucial to me for the success of >> asciidoc.
I don't have anything to add that I haven't already covered in my previous post other than to concur with Lex. If a Python3 port is sufficiently interesting or necessary to others then there's no reason they can't go ahead do it (that's the neat thing about OSS). Cheers, Stuart >> >> Why? System admins do not like to have several Python versions on their >> servers. If we had a python 3 version it would be easy to install asciidoc >> aside with other markup languages. Markup languages are getting >> more and more popular as the are offered on many sites for cooperate >> online editing. A python 3 version would significantly increase the >> availability of asciidoc and thus it's popularity. > > Well, most of my sysadmins are still welded to Python2 on old Redhat > versions, yours must be more adventurous :) > >> >> Asciidoc is well documented and the cheat-sheet is a very good start >> for beginners. In addition a life editor >> (like http://sourceforge.net/p/retext/home/ReText/) would ease the learning >> of asciidoc and contribute to increase its popularity also. >> These tools already rely on python 3. We discussed the topic here: >> https://groups.google.com/d/topic/asciidoc/0p8l1qD8-40/discussion >> >> Besides time and motivation who could migrate the code to python 3? >> Of course there are many python gurus out there. Maybe it is possible >> to find someone able to do it. > > I can't talk for Stuart, but I was not trying to imply that someone > shouldn't do it, just explaining that I don't have the time or much > inclination to do so. > > Thats why I posted my thoughts on encoding :) > > Although a big part of the process can be >> automated, there is a risk introducing a bunch of regression bugs. > > And this is the biggest problem, documents are things that get > archived, changing tools so they can no longer be used is *really bad* > (tm). > > >> Therefore the migration should be preferably done by the asciidoc core >> team, knowing the code well enough to identify the critical parts in >> advance. > > It may be preferable, but, for me anyway is unlikely to happen, unless > you sort out a means of deforming time separate from space so I have > 55 hours a day, but then I suspect the home boss will find things to > fill that :) > >> >> As I understand the asciidoc core team is Stuart and Lex? >> I imagine it is mainly a matter of time and resources, so maybe it is >> possible to delegate some of your tasks to someone else? For example code >> maintenance could be done without knowing all implementation details. >> Documentation also. Then you would have more time to concentrate >> on more strategical tasks like migration ;) >> > > Maintenance, answering emails etc are things that only take a few > minutes at a time. Porting to Python 3 is something that will take a > lot of concentrated time, it can't be done a few minutes at a time. > And at least for me, that simply isn't available. > > >> Cheers >> >> >> >> Jens >> >> -- >> You received this message because you are subscribed to the Google Groups >> "asciidoc" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/asciidoc/-/YLPmeKc_JrAJ. >> >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/asciidoc?hl=en. > -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
