Message194055
| Author | pitrou |
|---|---|
| Recipients | Arfrever, amaury.forgeotdarc, christian.heimes, gregory.p.smith, pitrou, python-dev, sbt |
| Date | 2013-08-01.12:23:41 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1375359821.13.0.0215219004833.issue18214@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Here (Linux) I get the following: # purge/gc os.path 12 # purge/gc operator 50 # purge/gc io 49 # purge/gc _sysconfigdata 48 # purge/gc sysconfig 47 # purge/gc keyword 46 # purge/gc site 45 # purge/gc types 44 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. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-08-01 12:23:41 | pitrou | set | recipients: + pitrou, gregory.p.smith, amaury.forgeotdarc, christian.heimes, Arfrever, python-dev, sbt |
| 2013-08-01 12:23:41 | pitrou | set | messageid: <1375359821.13.0.0215219004833.issue18214@psf.upfronthosting.co.za> |
| 2013-08-01 12:23:41 | pitrou | link | issue18214 messages |
| 2013-08-01 12:23:41 | pitrou | create | |