The templating is working as designed and it's pretty responsive
subjectively speaking. For those who might be interested, I'll post
some code and benchmarks after taking some time to clean up the code
and figure out a safe way to use eval within the template.
You should avoid 'eval',
Suggestion,
def fib(n):
a, b = 0, 1
while b n:
print(str(b) + , )
a, b = b, a+b
return b-a
var = fib(100)
%
brbr
{var}
%
Would make it python compatible, wsgi compatible, unit test
compatible, import compatible, eval
On Dec 10, 5:32 am, Graham Dumpleton [EMAIL PROTECTED]
wrote:
I have been asked something similar a number of times. I don't know
why but it is always to me direct and not on the mailing list. Not
sure if it means the others were embarrassed about their yearnings for
something more like PHP
On Dec 10, 1:52 pm, gert [EMAIL PROTECTED] wrote:
So let me get this straight, you are going to rewrite all this parsing
cashing ch*t in python, just you can have your own templates ?
That's part of the motivation. The rest is the desire to have the
option to choose pure WSGI application
On Dec 10, 2:24 pm, gert [EMAIL PROTECTED] wrote:
Am I the only one here that thinks this is a bad approach (i said
approach not idea)
I mean you go from mod_wsgi and make it act as a cripple mod_scgi with
GIL stuff and no stdout to transform it into mod_php using a
interpreter that execute
