2010/8/28 Alex Gaynor <alex.gay...@gmail.com>: > With all due respect: no. The template system is intentionally not > Python, this is a strong design decision and I see no compelling > argument against it here. If you're just generally interested in the > compilation of Django templates to PYthon (without changing the > current semantics) I suggest you take a look at : > http://www.mail-archive.com/django-developers@googlegroups.com/msg25147.html, > which was a GSOC proposal I wrote (and ultimately withdrew in favor of > my query-refactor work), it presents a method for translation of > Django templates into Python code, while maintaing the current > semantics.
Frankly, this is not what I did and I'm not interested about that. > As a small sidenote, when proposing a change a patch should contain a > single change, rather than a number of unrelated ones. Thank you very much for the lesson!!!! But I already knew. It would have taken time to produce different patches and test every single one (as many of them are NOT unrelated) when what I just wanted to know was if you were interested in my template system, and this was only a demostration version. Then if you were interested, I would have refined the work and then produced the single patch. As a small sidenote, I was not proposing a change but something to add if you would have read carefully my email. As a second small sidenote, I'm glad that I didn't waste my time. Thanks, Gabriele -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
