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 pitrou
Recipients Stan.Seibert, asksol, brandon-rhodes, catalin.iacob, christian.heimes, dholth, gregory.p.smith, jnoller, mrmekon, ned.deily, neologix, numbernine, pitrou, python-dev, rcoyner, sbt, vsekhar
Date 2013-08-14.15:37:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> I do see a couple of failed assertions on Windows which presumably
> happen in a child process because they do not cause a failure:
>     Assertion failed: !collecting, file ..\Modules\gcmodule.c, line
>     1617
> The assertion is in _PyGC_CollectNoFail() and checks that it is not
> called recursively.  See

That's extremely weird. _PyGC_CollectNoFail() is only called from
PyImport_Cleanup, which itself is only called from Py_Finalize()
and Py_EndInterpreter(). It should be basically impossible for the
GC to be already collecting garbage at that point... 

Perhaps you could try to find out in which test this happens?
Date User Action Args
2013-08-14 15:37:36pitrousetrecipients: + pitrou, gregory.p.smith, christian.heimes, ned.deily, jnoller, rcoyner, asksol, dholth, brandon-rhodes, neologix, catalin.iacob, python-dev, sbt, numbernine, vsekhar, mrmekon, Stan.Seibert
2013-08-14 15:37:36pitroulinkissue8713 messages
2013-08-14 15:37:36pitroucreate