On Apr 27, 11:45 pm, Michal M wrote:
> I've just found out that one of objects is not destroyed when it
> should be. This means that something was holding reference to this
> object or part of it (i.e. method). Is there any way to check what
> holds that reference? I am unable to do that just look
On Apr 28, 3:59 pm, Christian Heimes wrote:
> The trick works only for objects that are tracked by CPython's garbage
> collector. Simple and non-containerish objects like str, int, unicode
> and some other types aren't tracked by the gc.
Yes they are -- have you ever tried
>>> import gc
>>>
Almar Klein wrote:
Ah, it does exist! I wish I knew that two months ago, it would've saved me
some precious time ;)
The trick works only for objects that are tracked by CPython's garbage
collector. Simple and non-containerish objects like str, int, unicode
and some other types aren't tracked
On 27 April 2010 23:08, Chris Rebert wrote:
> On Tue, Apr 27, 2010 at 1:45 PM, Michal M
> wrote:
> > I've just found out that one of objects is not destroyed when it
> > should be. This means that something was holding reference to this
> > object or part of it (i.e. method). Is there any way to
On Apr 28, 12:02 am, Chris Rebert wrote:
> On Tue, Apr 27, 2010 at 2:58 PM, Chris Rebert wrote:
> > On Tue, Apr 27, 2010 at 2:42 PM, Michal M
> > wrote:
> >> On 27 Kwi, 23:21, Duncan Booth wrote:
> >>> Michal M wrote:
> >>> > I've just found out that one of objects is not destroyed when it
>
On Tue, Apr 27, 2010 at 2:58 PM, Chris Rebert wrote:
> On Tue, Apr 27, 2010 at 2:42 PM, Michal M wrote:
>> On 27 Kwi, 23:21, Duncan Booth wrote:
>>> Michal M wrote:
>>> > I've just found out that one of objects is not destroyed when it
>>> > should be. This means that something was holding refe
On Tue, Apr 27, 2010 at 2:42 PM, Michal M wrote:
> On 27 Kwi, 23:21, Duncan Booth wrote:
>> Michal M wrote:
>> > I've just found out that one of objects is not destroyed when it
>> > should be. This means that something was holding reference to this
>> > object or part of it (i.e. method). Is th
On 27 Kwi, 23:21, Duncan Booth wrote:
> Michal M wrote:
> > Hi
>
> > I've just found out that one of objects is not destroyed when it
> > should be. This means that something was holding reference to this
> > object or part of it (i.e. method). Is there any way to check what
> > holds that refere
Michal M wrote:
> Hi
>
> I've just found out that one of objects is not destroyed when it
> should be. This means that something was holding reference to this
> object or part of it (i.e. method). Is there any way to check what
> holds that reference? I am unable to do that just looking to the c
On Tue, Apr 27, 2010 at 1:45 PM, Michal M wrote:
> I've just found out that one of objects is not destroyed when it
> should be. This means that something was holding reference to this
> object or part of it (i.e. method). Is there any way to check what
> holds that reference? I am unable to do th
> I've just found out that one of objects is not destroyed when it
> should be. This means that something was holding reference to this
> object or part of it (i.e. method). Is there any way to check what
> holds that reference? I am unable to do that just looking to the code
> or debugging it beca
Michal,
May I ask why do you care about the object's management? Let Python worry
about that. What's your use case?
--
http://mail.python.org/mailman/listinfo/python-list
Hi
I've just found out that one of objects is not destroyed when it
should be. This means that something was holding reference to this
object or part of it (i.e. method). Is there any way to check what
holds that reference? I am unable to do that just looking to the code
or debugging it because it
13 matches
Mail list logo
