On Wed, 10 Sep 2014 01:04:02 PM Mike Bayer wrote:
In this case it appears to be a “safety” in case someone uses the
ConnectionContext object outside of being a context manager. I’d fix that
and require that it be used as a context manager only.
Oh look, I have a new pylint hammer that is
After some research, i find the reason for the cycle reference. In closure, the
_fix_paswords.func_closre reference the _fix_passwords. So the
cycle reference happened.
And in https://thp.io/2012/python-gc/python_gc_final_2012-01-22.pdf page 5, it
says that
We observe that Python
On Sep 10, 2014, at 4:11 AM, Li Tianqing jaze...@163.com wrote:
After some research, i find the reason for the cycle reference. In closure,
the _fix_paswords.func_closre reference the _fix_passwords. So the
cycle reference happened.
And in
Hello,
I use backdoor of eventlet to enable gc.DEBUG_LEAK, and after wait a few
minutes, i can sure that there will some objects that can not be collected by
gc.collect in gc.garbage.
Those looks like this (catched in ceilometer-collector)
['_context_auth_token', 'auth_token',
