Hey Jeremy James can you share this setup for webpy #extends, import in webpy please
I use Cheetah with pre-compiled templates - it's very fast *(the templates import especially quickly when python compiled and optimised). A bit of magic with the imp module takes a template name and a base directory (configured in a site-specific config) and loads up that template, taking care of #extends and #import directives as appropriate.* Thanks a lot On Tue, Mar 20, 2007 at 5:28 PM, Jeremy <[email protected]> wrote: > > For a production site, I use Cheetah with pre-compiled templates - > it's very fast (the templates import especially quickly when python > compiled and optimised). A bit of magic with the imp module takes a > template name and a base directory (configured in a site-specific > config) and loads up that template, taking care of #extends and > #import directives as appropriate. I don't use the built-in support > for Cheetah, however. The new template library is also only imported > to display the debugerror page. > > On Mar 20, 1:00 am, Jack <[email protected]> wrote: > > I also read in a review article that web.py only supports cheetah 1.0. > > Is that still the case? > > I'd be surprised by this (although not sure because we use debian > stable which is still on version 0.9.16) - after all, Cheetah simply > takes a template, fills it, and returns a string (possibly unicode). > Perhaps only the built-in cheetah module isn't compatible? > > -jeremy > > > > > -- Bidegg worlds best auction site http://bidegg.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
