Add Python support

[GoogleCodeExporter]

It would be great to be able to compile Soy templates to Python.

Original issue reported on code.google.com by dinob...@googlemail.com on 8 Nov 2009 at 8:15

[GoogleCodeExporter]

Sorry, there are no current plans to add Python support.

Original comment by kai.hu...@gmail.com on 13 Nov 2009 at 11:00

• Changed state: WontFix
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

would you take outside contributions for this?

Original comment by dol...@gmail.com on 27 Jul 2010 at 9:04

[GoogleCodeExporter]

If you were to actually write a high quality backend implementation of Soy for 
Python, with support for all the current features, then I'm sure we would be 
happy to add it to the project.  The main problem would be that going forward, 
we wouldn't have the resources to maintain it when we add new features to the 
other backends, and it may even break if we make certain large changes 
(probably not often though).  But if you're willing to maintain the Python 
backend when it gets broken or to implement key new features, I'd say go for it!

PS. I'm going to be on leave for most of Q3, so it would be Q4 before it can be 
added to the main project.

PPS. I think I recognize you as a Xoogler? Is that right?

Original comment by kai.hu...@gmail.com on 1 Aug 2010 at 4:55

[GoogleCodeExporter]

This is confusing to me. I could not find a Soy for Python. Is it that I looked 
at the wrong places? Is dolapo or somebody else still working on a port?

Is there some research / dialog available on the benefits of having server side 
templates in an Ajax application. I think mainly the data exchange will be XHR 
but I can think of cases where a server side template could be helpful like 
creation of the initial html page.

Original comment by m...@testing-software.org on 14 May 2012 at 4:53

[GoogleCodeExporter]

I think there are some 3rd party Python implementations of Soy. Obviously, I 
can't vouch for their accuracy in behavior and features.

I'll also keep an eye out for engineers inside Google who want to add a Python 
backend to Soy.

Original comment by k...@google.com on 14 May 2012 at 7:40

[GoogleCodeExporter]

The issue is closed now, but just FYI, I'm working on adding Python backend at 
https://bitbucket.org/lalinsky/closure-templates/overview

Should I submit a patch when I'm done? Would an external contribution be 
accepted?

Original comment by lalinsky on 28 Feb 2014 at 11:04

[GoogleCodeExporter]

https://oxygene.sk/2014/03/closure-templates-soy-for-python/

Original comment by lalinsky on 12 Mar 2014 at 6:25

[GoogleCodeExporter]

Wow, awesome! Thanks for this! This is actually something someone else was 
looking at internally... I didn't catch a glimpse of this until now. I'm going 
to touch base with the engineer who has been working on this.

One very unfortunate thing is that we been far too lazy in updating the open 
source version of Soy, so it's likely there will be a large version gap; in the 
next version we have much better support for strict autoescaping, for example. 
Once we get our open source version up to date (I can't guarantee when that 
will be unfortunately) we can see whether it is still convenient to patch, or 
whether the person working on it internally is close enough to something 
workable that it makes sense just to finish that.

Thanks again! This is amazing!

Original comment by gbo...@google.com on 16 Apr 2014 at 6:02