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 serhiy.storchaka
Recipients eric.snow, serhiy.storchaka, vstinner
Date 2017-03-22.17:16:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1490203009.58.0.867795444212.issue29881@psf.upfronthosting.co.za>
In-reply-to
Content
The problem with existing static variables are that they are not properly cleared. When the Python interpreter is finalized and reinitialized they can contain invalid references. This patch fixes this issue.

> * It requires to write "var.obj" instead of just "var" to access the Python object

You can use a dynamic array of PyObject** instead of a linked list for collecting references to "static variables" or use gc_next/gc_refs for managing a linked list.
History
Date User Action Args
2017-03-22 17:16:49serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner, eric.snow
2017-03-22 17:16:49serhiy.storchakasetmessageid: <1490203009.58.0.867795444212.issue29881@psf.upfronthosting.co.za>
2017-03-22 17:16:49serhiy.storchakalinkissue29881 messages
2017-03-22 17:16:49serhiy.storchakacreate