Hello, I made all tests green finally (all commits are tested under Python
2.7.3 and 3.2.3). The problem that took a few days to solve was that the
default engine should be recomputed after changing TEMPLATE_LOADERS setting
since its _template_source_loaders internal needs to be recalculated. I
Hi Christopher,
> OK, let mi introduce the idea for Google Some Of Code of this year. The
idea is stolen from Pyramid [3]. The main new concept is a renderer. A
renderer may be current TemplateEngine as well as JSON serializer or mako
renderer.
I can't really comment on if it'd be appropriate
Hello. I would like to report progress of my work (not too much new things,
rather cleaning and polishing), discuss some issues and propose an idea for
next Google Summer Of Code.
Progres from last time:
- Solved problem with TemplateResponse -- it receives optional keyword
argument
For anyone developing a SaaS that allows users to create templates through the
UI (e.g., a hosted CMS), separately initializable template system is paramount,
giving the ability to modify multiple settingsin the template system that are
in effect during template rendering, including loaders,
Hello Christopher,
On 02/08/2013 09:59 AM, Christopher Medrela wrote:
> I don't want to discourage you from working on the project if you find
>
> it interesting and informative, and it may well be that the results are
>
> worth the effort and end up being merged into Django; but it
Hello. I'm really astonished how fast I get feedback and I really
appreciate that. I apologize that you had to wait for my reply so long, but
I cannot push myself to stop programming and to share results. :)
I did some progress since creating this topic:
- Almost all tests doesn't rely on
On Monday, January 28, 2013 9:30:44 AM UTC-8, Christopher Medrela wrote:
>
> Hello everybody.
>
> 1. I'm working on ticket #17093 [1]. You can see progress of work at
> github [2]. It's about rewritting django.template so it won't use global
> state. I wrote this post to tell you what I did
Hi Christopher,
Some feedback below.
> 2. This package has two kinds of global state. The first one are global
> attributes defined at module level of template package. These are
> base.builtins, base.libraries, loader.template_source_loaders and
> base.templatetags_modules. The second one
Hello Christopher,
Since I opened that ticket and sent you down this rabbit-hole, I can at
least offer some thoughts :-) In full disclosure, I should also say that
since opening the ticket I've had doubts about whether this change
(although clearly an improvement in the abstract) is worth the
Hello everybody.
1. I'm working on ticket #17093 [1]. You can see progress of work at github
[2]. It's about rewritting django.template so it won't use global state. I
wrote this post to tell you what I did so far, what issues I deal with and
to discuss them. I hope that we will gain valuable
10 matches
Mail list logo