Massimo, That's what i respect of you.. To the point explanation. Cheers!!!
Regards, *Yogesh * On Mon, May 7, 2012 at 4:12 AM, Massimo Di Pierro < [email protected]> wrote: > First of the comment about what web2py "allegedly" does is untrue. Web2py > does not inject variables in modules. Web2py leaves modules alones and you > use them normally as in any python program. Web2py simpley does not treats > models and controllers as modules. They in are not modules at all. They are > executed in a context not imported. > > Yes this is a source of criticism mostly for people who do not understand > why we do it (to enable hot install and uninstall of apps without > conflicts). It is better than what other frameworks do (reload module when > they change and that can cause memory leaks and other problems) and yet do > not achieve the clean multi-app support that web2py has. > > I have tried rewriting web2py without the exec mechanism. It cannot be > done without giving up some of our unique features. We can make it a little > cleaner (there is a meta-programming step that can be eliminated). We can > promote parts of models to modules so that tables are defined once and for > all. Still working on it anyway. Any feedback is appreciated. > > Massimo > > On Sunday, 6 May 2012 13:10:36 UTC-5, pbreit wrote: >> >> Would making it so that you "import request" satisfy the author? It does >> seem like web3py (or whatever) whould make more use of import to avoid >> these critiques. > >
