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 nascheme, pablogsal, serhiy.storchaka, tim.peters, twouters, vstinner
Date 2019-10-07.11:42:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1570448528.2.0.416187203627.issue38392@roundup.psfhosted.org>
In-reply-to
Content
From documentation:

.. c:function:: void PyObject_GC_Track(PyObject *op)

   Adds the object *op* to the set of container objects tracked by the
   collector.  The collector can run at unexpected times so objects must be
   valid while being tracked.  This should be called once all the fields
   followed by the :c:member:`~PyTypeObject.tp_traverse` handler become valid, usually near the
   end of the constructor.

So there was a bug in Modules/pyexpat.c.
History
Date User Action Args
2019-10-07 11:42:08serhiy.storchakasetrecipients: + serhiy.storchaka, tim.peters, twouters, nascheme, vstinner, pablogsal
2019-10-07 11:42:08serhiy.storchakasetmessageid: <1570448528.2.0.416187203627.issue38392@roundup.psfhosted.org>
2019-10-07 11:42:08serhiy.storchakalinkissue38392 messages
2019-10-07 11:42:08serhiy.storchakacreate