Any plans for Python 3

[chris...@gmail.com]

Hi, 

I'm in the process of porting tiddlywebwiki[1] so it works in both Python 2 and 3. WikklyText is used in there to do server-side rendering of tiddlywikitext. Is WikklyText alive and well and if so are there plans to support both versions of Python?

[1] https://github.com/tiddlyweb/tiddlywebwiki

[Frank McIngvale]

Unfortunately not, I think it has dropped far enough down on my priority list you could consider it dead from my perspective. Having said that, I don't believe it would be incredibly hard to port to Python 3, since internally the code has always been Unicode-centric. I have a vague recollection of having run it through the 2to3 tool at some point without significant issues but have no plans to "officially" do anything there.

As you know, WikklyText includes a lot of its own server-side code since that was its original purpose, but I always kept it modular so if you want to make your own subset with just the rendering parts and port that to Python 3, go for it! I have no further plans for it, so that wouldn't cause any issues with needing to merge changes later, etc.

Frank

--
You received this message because you are subscribed to the Google Groups "WikklyText" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wikklytext+...@googlegroups.com.
To post to this group, send email to wikkl...@googlegroups.com.
Visit this group at http://groups.google.com/group/wikklytext.
For more options, visit https://groups.google.com/groups/opt_out.

[chris...@gmail.com]

On Thu, 14 Nov 2013, Frank McIngvale wrote:

> Unfortunately not, I think it has dropped far enough down on my priority
> list you could consider it dead from my perspective. Having said that, I
> don't believe it would be incredibly hard to port to Python 3, since
> internally the code has always been Unicode-centric. I have a vague
> recollection of having run it through the 2to3 tool at some point without
> significant issues but have no plans to "officially" do anything there.

That's what I expected, just wanted to confirm.

> As you know, WikklyText includes a lot of its own server-side code since
> that was its original purpose, but I always kept it modular so if you want
> to make your own subset with just the rendering parts and port that to
> Python 3, go for it! I have no further plans for it, so that wouldn't cause
> any issues with needing to merge changes later, etc.

Thanks, I'll look into it. It's hard to be sure about what the right
thing to do is. While the vast majority of people using tiddlyweb are
using it with the tiddlywiki and tiddlywikitext, most of the people
doing development are not using tiddlywiki as a client and are using
markdown as the text format.

--
Chris Dent http://burningchrome.com/
[...]