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 martin.panter
Recipients Alexey Kazantsev, Vadim Markovtsev, amaury.forgeotdarc, martin.panter, pitrou, serhiy.storchaka
Date 2015-03-21.11:38:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1426937884.33.0.147659895025.issue23720@psf.upfronthosting.co.za>
In-reply-to
Content
There is a cycle involving the class object, but I don’t think there is a cycle involving the instance objects this time.

However, I wonder if __del__() is meant to be called in any particular order anyway. What’s to stop the garbage collector itself from creating a temporary reference to the Device instance, destroying the Vector instance, which invokes Vector.__del__(), and finally destroying the temporary reference to the Device instance?
History
Date User Action Args
2015-03-21 11:38:04martin.pantersetrecipients: + martin.panter, amaury.forgeotdarc, pitrou, serhiy.storchaka, Vadim Markovtsev, Alexey Kazantsev
2015-03-21 11:38:04martin.pantersetmessageid: <1426937884.33.0.147659895025.issue23720@psf.upfronthosting.co.za>
2015-03-21 11:38:04martin.panterlinkissue23720 messages
2015-03-21 11:38:04martin.pantercreate