On Wed, Nov 07, 2012 at 01:27:33PM +0100, Marc Espie wrote:
> Actually, we discussed a possible approach. It looks reasonable to have a
> "compile as package" mode (say through an env variable for instance) that
> would disable the check and leave a mark in the compiled file that says the
> check
On Wed, Nov 07, 2012 at 11:05:23AM +, Laurence Tratt wrote:
> On Mon, Nov 05, 2012 at 02:15:53PM +0100, Marc Espie wrote:
>
> > Turns out python is stupid enough to store path+timestamp in its compiled
> > *.pyc files to know when to recompile.
>
> The "auto-recompile everything which is out
On Mon, Nov 05, 2012 at 02:15:53PM +0100, Marc Espie wrote:
> Turns out python is stupid enough to store path+timestamp in its compiled
> *.pyc files to know when to recompile.
The "auto-recompile everything which is out of date" feature is ingenious but
there are at least two different ways of
sthen@ finally figured out most of the problem.
Turns out python is stupid enough to store path+timestamp in its compiled
*.pyc files to know when to recompile.
Our package system doesn't look to closely at timestamps... so this explains
how *.pyc files sometimes get rebuilt, and then throw erro
