Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2003-February/033032.html below:

[Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail

• Previous message: [Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail
• Next message: [Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[Fred L. Drake, Jr.]
> Why would creating new style classes create cycles?  The links between
> a type and derived types use weak references, which do not rely on the
> cycle GC support.

>>> def f():
...    class C(object):
...       pass
...
[9589 refs]
>>> f()
[9611 refs]
>>> f()
[9632 refs]
>>> f()
[9653 refs]
>>> f()
[9674 refs]
>>> f()
[9695 refs]
>>> f()
[9716 refs]
>>> f()
[9737 refs]
>>> f()
[9758 refs]
>>> import gc
[9900 refs]
>>> gc.collect()
48
[9742 refs]
>>>

Take it from there, but don't forget to come for air once an hour <wink>.

• Previous message: [Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail
• Next message: [Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4