The memory leak is a meme. The argument goes like this. Instantiating objects with a __del__method and a self reference causes a memory leak. This is True.
The fact is, web2py does not do it. Moreover the same argument applies to any python program and any python web framework. It is a consequence of the choice to use reference counting instead of garbage collection in Python. But again, we do not do it and, in the book, we clearly tell users not to create objects with __del__ methods. Is it possible that we have a memory leak? I guess, yes. In fact there is a a bug report from last week about it and we are investigating. So far, I cannot reproduce it and it does not seem to have affected users. Moreover this is a new issue and as always we will investigate and resolved it. It shows we take memory consumption seriously and as openly as we can. The web2py design in fact uses less memory than other frameworks with lots of modules because only the controller in execution stays in ram. All the other frameworks keep all the code in ram whether or not it is in execution. Massimo On Thursday, 29 March 2012 19:22:25 UTC-5, Derek wrote: > > I've been using python for the past 12 years, I think web2py is one of the > best designed full feature python frameworks around. The only complaints I > see people make are "from gluon.tools import *" which is not a concern for > me - if you're going to be working on something, it's nice to have those > tools already attached to your suit. and "memory leaks". I've never > encountered a memory leak in my experience of using web2py. > > If you're going to listen to the lead developer of django, then use his > software. If you're going to listen to the developer of web2py, use his > software. I don't care. I'm just glad I picked a framework that does what I > need. Forget all this noise about which is the "best". > > Looking at it another way, am I going to choose something that was > designed by committee, or something designed by a Ph.D who teaches > development and web security? > > On Wednesday, March 28, 2012 8:06:28 AM UTC-7, glimmung wrote: >> >> Hi, >> >> On 28/03/2012 15:08, nick name wrote: >> > Come say the good things you have to say about web2py on >> > http://news.ycombinator.com/item?id=3765610 >> >> Late catching up here because I've been following that! >> >> Had to call the Django guy out on his (completely unsupported) statement >> that web2py is "a fundamentally incorrect way to approach web >> development", a statement that he made *AFTER* admitting that he'd never >> used it! >> >> Not being a fan of flame-wars, I try to restrict myself to establishing >> whether people who criticise web2py have actually used it - so far 100% >> of critics that I've encountered have /not/ used it, which I think >> speaks volumes... >> >> -- >> >> Regards, >> >> PhilK >> >> >> 'a bell is a cup...until it is struck' >> >>
