If we can't fix the memory leak, can we at least have the code detect the Python version and use the faster Storage in case >= 2.7.3, or are there too many places where code would need to change to make that practical?
Anthony On Wednesday, August 22, 2012 9:28:59 AM UTC-4, Massimo Di Pierro wrote: > > We run into a major problem. The Storage improvements in trunk cause a > memory leak. > This is a python bug and it was discovered in 2006.: > > http://bugs.python.org/issue1469629 > > Apparently this was only fixed in python 3.2 and python 2.7.3. > > Not sure what to do but at the moment I do not see any solution than > removing the improvements. > > massimo > > > > > On Wednesday, 22 August 2012 01:44:44 UTC-5, Johann Spies wrote: >> >> I hope that web2py 2.0 will not be released without these improvements >> even if it means that testing it will delay the release. >> >> Thanks to the developers for their initiatives and ingenuity. >> >> Regards >> Johann >> -- >> Because experiencing your loyal love is better than life itself, >> my lips will praise you. (Psalm 63:3) >> >> --
