This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author arigo
Recipients arigo, neologix, nikratio, pitrou, serhiy.storchaka, vstinner
Date 2014-12-04.10:24:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1417688682.2.0.0328311025386.issue17852@psf.upfronthosting.co.za>
In-reply-to
Content
If I understood correctly, Python 3.4 tries harder to find cycles and call destructors at the end of the program, but that's not a full guarantee.  For example you can have a reference from a random C extension module.

While trying to come up with an example, I found one that I don't fully understand, but the point is that it shows how easy it is to defeats it:

    import sys
    f = open('foo.txt', 'w')
    f.write('abc')
    def func(*args):
        return func
    sys.settrace(func)
History
Date User Action Args
2014-12-04 10:24:42arigosetrecipients: + arigo, pitrou, vstinner, nikratio, neologix, serhiy.storchaka
2014-12-04 10:24:42arigosetmessageid: <1417688682.2.0.0328311025386.issue17852@psf.upfronthosting.co.za>
2014-12-04 10:24:42arigolinkissue17852 messages
2014-12-04 10:24:41arigocreate