"Asaf Las" wrote in message
news:9729ddaa-5976-4e53-8584-6198b47b6...@googlegroups.com...
> On Wednesday, January 22, 2014 10:56:30 AM UTC+2, Frank Millman wrote:
>>
>> class MainObject:
>> def __init__(self, identifier):
>> self._del = delwatcher('MainObject', identifier)
>> class
Asaf Las Wrote in message:
> On Wednesday, January 22, 2014 10:56:30 AM UTC+2, Frank Millman wrote:
>>
>> class MainObject:
>> def __init__(self, identifier):
>> self._del = delwatcher('MainObject', identifier)
>> class delwatcher:
>> def __init__(self, obj_type, identifier):
>>
On Wednesday, January 22, 2014 10:56:30 AM UTC+2, Frank Millman wrote:
>
> class MainObject:
> def __init__(self, identifier):
> self._del = delwatcher('MainObject', identifier)
> class delwatcher:
> def __init__(self, obj_type, identifier):
> self.obj_type = obj_type
>
On Wednesday, January 22, 2014 10:43:39 AM UTC+2, Nicholas wrote:
> There are some good tools recommended here:
> http://stackoverflow.com/questions/110259/which-python-memory-profiler-is-recommended
> But in general: use weak references wherever possible would be
> my advice. They not only prev
"Asaf Las" wrote in message
news:58c541ab-c6e1-45a8-b03a-8597ed7ec...@googlegroups.com...
>
> Yes the question was about CPython. But i am not after CPython leaks
> though detecting these would be good, but my own mistakes leading to
> accumulation of data in mutable structures.
> there will be
On Wednesday, 22 January 2014, Asaf Las wrote:
> On Wednesday, January 22, 2014 5:08:25 AM UTC+2, Chris Angelico wrote:
> > I assume you're talking about pure Python code, running under CPython.
> > (If you're writing an extension module, say in C, there are completely
> > different ways to detec
On Wednesday, January 22, 2014 5:08:25 AM UTC+2, Chris Angelico wrote:
> I assume you're talking about pure Python code, running under CPython.
> (If you're writing an extension module, say in C, there are completely
> different ways to detect reference leaks; and other Pythons will
> behave slight
On Wed, Jan 22, 2014 at 1:51 PM, Asaf Las wrote:
> When designing long running background process
> is it feasible to monitor object/memory leakage due
> to improper programming?
I assume you're talking about pure Python code, running under CPython.
(If you're writing an extension module, say in
Hi
When designing long running background process
is it feasible to monitor object/memory leakage due
to improper programming?
If it could be possible to make module which monitor and
record trends if alive objects then event can be
generated and logged if noof "zombie" objects
are to increa
