@Massimo- you're saying a production application should not reload modules, but then what is the correct process for updating an app in production - i.e. installing an app by overwriting an old one - if it has modules that have changed?
On Sunday, April 29, 2012 12:02:52 PM UTC-4, Massimo Di Pierro wrote: > > Let's clarify something.... > > web2py always uses the most comment models/controllers/views. > web2py (as Python does) loads modules onces and keeps them in memory, even > when modules are shipped with the app. > The fact that > > from gluon.custom_import import track_changes; track_changes(True) > > overrides this behavior if a feature to be used in development, not in > production. > > Reloading modules is a bad idea. It has performance penalties and can > cause undesired effects because of global objects defined in the modules. > A production application should not do this. > > > > On Sunday, 29 April 2012 08:34:26 UTC-5, Yarin wrote: >> >> Got to say this is scary- we're about to go into production with our >> first web2py app, and having erratic module behavior persist across server >> restarts is not something we signed up for. Please let's address this. >> >> On Sunday, April 29, 2012 9:12:55 AM UTC-4, Yarin wrote: >>> >>> @Bruno- Thanks for confirming this issue >>> @Anthony - Thoughts? >>> >>> >>>>
