On Jan 9, 7:15 pm, jthibeaux <[EMAIL PROTECTED]> wrote: > I am using TurboGears1.4.3.b, and it seems that on our production > environment under Linux, even when the python sources have all been > updated, restarting the server does not cause all the sources to be > recompiled and the old version continues to be used. Only after I > made another update to the startup script did I manage to get new code > to be used. Is there another way to guarantee that everything gets > recompiled? I haven't been using TurboGears or Python for very long, > so please forgive me if there is a simple explanation. > > One thing to note is that we have changed autoreload.on to False since > this caused a threading conflict with Lucene, but I wouldn't figure > that should matter when the entire server is restared. Is anyone else > having a similar problem? Is this a CherryPy issue? Is this a Python > issue?
Hi Jeremy, I had similiar problems, source of it was the timestamp of the files, maybe check what is the timestamp when you change the file, if you are uploading files over scp, the timestamps can remain from the uploading machine, so all in all you can have timestamps in the past, this is one of the reasons. You can add to start/stop script a removal of all *.pyc in the directory, might help, its not a solution for the error, only a way to deal with consequences. Regards -- Michal --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
