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 Arfrever, amaury.forgeotdarc, christian.heimes, gregory.p.smith, pitrou, python-dev, sbt
Date 2013-08-01.13:12:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375362735.69.0.489638925149.issue18214@psf.upfronthosting.co.za>
In-reply-to
Content
> Also, do note that purge/gc after wiping can still be a regular gc
> pass unless the module has been wiped. The gc could be triggered by
> another module being wiped.

That said, I welcome any suggestions to improve things. The ultimate
reasons we need to purge some modules are the same two reasons I
indicated on python-dev: C extension modules are almost immortal;
and some C code keeps references alive too long.

Do you agree that this patch is ok and we should address those two
problems in separate new issues?
History
Date User Action Args
2013-08-01 13:12:15pitrousetrecipients: + pitrou, gregory.p.smith, amaury.forgeotdarc, christian.heimes, Arfrever, python-dev, sbt
2013-08-01 13:12:15pitrousetmessageid: <1375362735.69.0.489638925149.issue18214@psf.upfronthosting.co.za>
2013-08-01 13:12:15pitroulinkissue18214 messages
2013-08-01 13:12:15pitroucreate