another approach i was thinking is the "import" approach something like import apache and import cgi but then import wsgi and import php where php module defines your template specification like php.echo for example. Its just a bit weird that the wsgi guy's put there heads together to redesign the cgi environment resulting into a wsgi standard where they consider print as something very very bad. And now we use there design to reinvent print again and name it echo :-)
Anyway i think Guido would have nightmares if "<% %>" emerged in his syntax. Actually in the end i think i would be easier to modify mod_php to work with python code. Maybe Graham can squeeze something in the mod_php source code, it suddenly starts running python code the php way as wel :-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to modwsgi@googlegroups.com To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
