Re: Cheetah's #include base directory

I don't think it's documented in the main docs.
Add:
   import Cheetah.ImportHooks
   Cheetah.ImportHooks.install()

somewhere early in your python process' startup.  The code is really old, 
pre pep-302, but I think it should still work.  If not, it should be easy 
enough to use http://pypi.python.org/pypi/importlib/1.0.1 to update it.

Tavis

On Tue, 16 Mar 2010, Aahz wrote:

> On Tue, Mar 16, 2010, Tavis Rudd wrote:
>>
>> Wouldn't template inheritance with dynamic compilation just require
>> installing the Cheetah import hook?
>
> Where is that documented?  This is the first I've heard of it, and I
> don't see it anywhere at
> http://www.cheetahtemplate.org/docs/users_guide_html/
> -- 
> Aahz ([email protected])           <*>         http://www.pythoncraft.com/
>
> "Many customs in this life persist because they ease friction and promote
> productivity as a result of universal agreement, and whether they are
> precisely the optimal choices is much less important." --Henry Spencer
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Cheetahtemplate-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/cheetahtemplate-discuss
>

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev