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 sbt
Recipients Arfrever, amaury.forgeotdarc, christian.heimes, gregory.p.smith, pitrou, python-dev, sbt
Date 2013-08-01.11:17:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375355844.87.0.23023177643.issue18214@psf.upfronthosting.co.za>
In-reply-to
Content
> I get different numbers from you. If I run "./python -v -c pass", most 
> modules in the "wiping" phase are C extension modules, which is expected. 
> Pretty much every pure Python module ends up garbage collected before 
> that.

The *module* gets gc'ed, sure.  But you can't tell from "./python -v -c pass" when the *module dict* get gc'ed.

Using "./python -v check_purging.py", before the purging stage (# cleanup [3]) I only get

# purge/gc operator 54
# purge/gc io 53
# purge/gc keyword 52
# purge/gc types 51
# purge/gc sysconfig 50

That leaves lots of pure python module dicts to be purged later on.
History
Date User Action Args
2013-08-01 11:17:24sbtsetrecipients: + sbt, gregory.p.smith, amaury.forgeotdarc, pitrou, christian.heimes, Arfrever, python-dev
2013-08-01 11:17:24sbtsetmessageid: <1375355844.87.0.23023177643.issue18214@psf.upfronthosting.co.za>
2013-08-01 11:17:24sbtlinkissue18214 messages
2013-08-01 11:17:24sbtcreate