Like Russ Magee said, Armin has a lot of experience in this field and
even if he didn't yet decided how to implement a compiled engine for
Django templates, I'm sure he will do a good job on this.
But that certainly doesn't mean that you shouldn't try as well (Even
when it's not accepted for GSoC)
Hello, Russell Keith-Magee
Thanks for your advices.
*1. Detailed Timeline :*
- Designing concept : this step requires fully design writing for
achieving BACKWARD compatibility for all tags, and filters. Providing
backward-compatibility is a simple task. I've described it earlier by using
On Fri, Apr 8, 2011 at 9:15 AM, Andrey Zubko wrote:
> Hello,
> I'm Andrey Zubko, student faculty of Computer Science in Zaporozhye
> State Engineering Academy. I'm senior chief developer of a local
> Internet Service Provider "Telza" which provides Internet and
> telephony services. My responsibil
Hello,
I'm Andrey Zubko, student faculty of Computer Science in Zaporozhye
State Engineering Academy. I'm senior chief developer of a local
Internet Service Provider "Telza" which provides Internet and
telephony services. My responsibilities includes enhancing, improving
existent Billing system tha
Hi, Jonathan
I was considering two approaches : template compilation with static
inheritance and template compilation with static and dynamic
inheritance.
The first one approach has simple way of compilation :
1.Reading template in string
2.Tokenizing
3.Parsing — creating NodeList structure
4.Recui
Another one:
Instead of:
def has_key(self,key):
for level in xrange(0,len(self._levels)) :
if self._levels[level].has_key(key) :
return True
return False
do:
def has_key(self,key):
return any((key in l) for l in self._levels)
Ony one "s
Hi Andrey
I haven't yet looked through all of your code, but already a little
feedback.
Remember that every dot operator requires a dictionary lookup or
getattr call. Also the [ ]-operator is another level of redirection. I
think using 'self' inside a for-loop is not a good idea. If you're
going
Hello, Jonathan
> How exactly do you want to solve dynamic inheritance? It seems that
> some people are still interested in dynamic inheritance, by using
{%
> extends variable %}. (Which is still dirty in my opinion, but
anyway.)
> Block information has to be kept somehow.
For supporting dynam
How exactly do you want to solve dynamic inheritance? It seems that
some people are still interested in dynamic inheritance, by using {%
extends variable %}. (Which is still dirty in my opinion, but anyway.)
Block information has to be kept somehow.
Maybe one small improvement. Isn't the followin
I'm interested in participating in your mentors program in Google
Summer Code.
Looking at the template implementation I've seen that I can make some
solutions for implementation compiling in bytecode templates. Just
adding function «compile» to every Node-derived class and modifying/
adding new f
10 matches
Mail list logo
