On Wed, Feb 3, 2010 at 11:02 AM, Christoph Zwerschke <c...@online.de> wrote:
> Kid uses similar logic. But if you're using TurboGears, then there is
> also TurboKid involved which does some caching. Do you have the latest
> version of TurboKid installed (1.0.5)? You can update with
> easy_install -U TurboKid
>
Thanks for the explanation. We're using 1.0.4.4 of Turbogears and can't
easily change versions (prod environment), but pre-compiling with "kidc -f"
seems to be a good workaround.
Correct me if I'm wrong, but it appears that the TurboKid logic is still
broken. Consider line 119 of kidsupport.py of TurboKid 1.0.5:
reload_modules = mtime > ttime
I've only spent ~5 minutes looking at the code, but it appears that TurboKid
only recompiles if the source file mtime is more recent than the .pyc file
mtime. If I'm understanding correctly, is it worth complaining on the
turbogears mailing list(s)?
Thanks,
Jason
--
Jason Rennie
Research Scientist, ITA Software
617-714-2645
http://www.itasoftware.com/
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
kid-template-discuss mailing list
kid-template-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kid-template-discuss
