Message183951
| Author | kristjan.jonsson |
|---|---|
| Recipients | Rhamphoryncus, amaury.forgeotdarc, barry, gregory.p.smith, jlaurila, jszakmeister, kristjan.jonsson, ncoghlan, neilo, pitrou, pjmcnerney, rhettinger, tlesher, vstinner |
| Date | 2013-03-11.11:30:19 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1363001420.07.0.861765772954.issue3329@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Absolutely. Although there is a very useful scenario where this could be consided a run-time setting: # turboprofiler.py # Load up the memory hooker which will supply us with all the info import _turboprofiler _turboprofiler.hookup() Perhaps people interested in memory optimizations and profiling could hook up at pycon? It is the most common regular query I get from people in my organization: How can I find out how python is using/leaking/wasting memory? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-03-11 11:30:20 | kristjan.jonsson | set | recipients: + kristjan.jonsson, barry, rhettinger, gregory.p.smith, amaury.forgeotdarc, ncoghlan, Rhamphoryncus, pitrou, vstinner, jszakmeister, tlesher, jlaurila, neilo, pjmcnerney |
| 2013-03-11 11:30:20 | kristjan.jonsson | set | messageid: <1363001420.07.0.861765772954.issue3329@psf.upfronthosting.co.za> |
| 2013-03-11 11:30:20 | kristjan.jonsson | link | issue3329 messages |
| 2013-03-11 11:30:19 | kristjan.jonsson | create | |