Author sbt
Recipients Arfrever, amaury.forgeotdarc, christian.heimes, gregory.p.smith, pitrou, python-dev, sbt
Date 2013-08-01.13:03:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <51FA5CA9.2080407@gmail.com>
In-reply-to <1375359821.13.0.0215219004833.issue18214@psf.upfronthosting.co.za>
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.

For me, the modules which die naturally after purging begins are

# purge/gc encodings.aliases 34
# purge/gc _io 14
# purge/gc collections.abc 13
# purge/gc sre_compile 12
# purge/gc heapq 11
# purge/gc sre_constants 10
# purge/gc _weakrefset 9
# purge/gc reprlib 8
# purge/gc weakref 7
# purge/gc site 6
# purge/gc abc 5
# purge/gc encodings.latin_1 4
# purge/gc encodings.utf_8 3
# purge/gc genericpath 2

Of these, all but the first appear to happen during the final cyclic 
garbage collection.
History
Date User Action Args
2013-08-01 13:03:46sbtsetrecipients: + sbt, gregory.p.smith, amaury.forgeotdarc, pitrou, christian.heimes, Arfrever, python-dev
2013-08-01 13:03:46sbtlinkissue18214 messages
2013-08-01 13:03:46sbtcreate