Am 03.02.2010 20:16 schrieb Jason Rennie: > On Wed, Feb 3, 2010 at 1:52 PM, Christoph Zwerschke wrote: > > Isn't that the expected behavior? > > Egad, no. That compiled file is only a valid substitute for the exact > source from which it was compiled. > ... Python only uses the .pyc if there is an exact timestamp match.
Oops. You're completely right with that. Sorry it took me so long to grasp the problem - somehow confused the mtime /of/ the .pyc file with the mtime /stored inside/ the .pyc. So yes, that's how Python handles it and it's completely reasonable. Kid does a similar thing, it stores the mtime of the template in the .pyc file, but then, as you noticed, only recompiles if the template file has a /newer/ mtime, not if it has an /older/ mtime. I agree that it makes sense to change Kid to behave in the same way. Will add it to the trac and implent it once it's running again. -- Christoph ------------------------------------------------------------------------------ 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
