Yes. because it depends on what module does. You should not do this in production. Many "other" frameworks treat models and controllers and they potentially suffer from this problem (depending on the module). This is why in web2py models and controllers are not modules, to avoid this problem. reloading modules is not good.
Massimo On Monday, 30 April 2012 09:32:40 UTC-5, Richard Galka wrote: > > I would also like to comment that I suspect (unconfirmed) that reloading > of modules while references are still around appears to potentially cause > memory leaks.. during dev while modules are reloaded, our app's memory > usage grows significantly. With this disabled, we find a consistent > footprint throughout the apps life. > > On Sunday, April 29, 2012 11:02:52 AM UTC-5, 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? >>>> >>>> >>>>>
