In fact I had two problems and thought they were related somehow. Well, they were not. The one described in my previous mail just happened in the test code I wrote. I never had it in a 'real' application. So maybe you're right this would be solved by the gc at some point.
The second is actually related to zope.interfaces and not pyramid. Though I've posted an issue with details on github ( https://github.com/Pylons/pyramid/issues/688). Looks like it's somehow related to the c code or caching. > > Also note that Python cannot free objects participating in a reference > cycle if they have __del__ methods on objects. > > No? I never thought of that. > I wrote http://pypi.python.org/pypi/objgraph when I was debugging a > memory leak in an app's test suite. It may help you narrow down the > leak, if there is one. > Thanks. I'll try it. Maybe it gives some more details. Arndt. -- DV Electric / Arndt Droullier / www.dvelectric.de -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
