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 | Rhamphoryncus |
|---|---|
| Recipients | Rhamphoryncus, barry, brett.cannon, jlaurila, ncoghlan, rhettinger |
| Date | 2008年07月10日.16:57:09 |
| SpamBayes Score | 0.05865316 |
| Marked as misclassified | No |
| Message-id | <1215709031.3.0.595533680838.issue3329@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Basically you just want to kick the malloc implementation into doing some housekeeping, freeing its caches? I'm kinda surprised you don't add the hook directly to your libc's malloc. IMO, there's no use-case for this until Py_Finalize can completely tear down the interpreter, which requires a lot of special work (killing(!) daemon threads, unloading C modules, etc), and nobody intends to do that at this point. The practical alternative, as I said, is to run python in a subprocess. Let the OS clean up after us. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月10日 16:57:11 | Rhamphoryncus | set | spambayes_score: 0.0586532 -> 0.05865316 recipients: + Rhamphoryncus, barry, brett.cannon, rhettinger, ncoghlan, jlaurila |
| 2008年07月10日 16:57:11 | Rhamphoryncus | set | spambayes_score: 0.0586532 -> 0.0586532 messageid: <1215709031.3.0.595533680838.issue3329@psf.upfronthosting.co.za> |
| 2008年07月10日 16:57:10 | Rhamphoryncus | link | issue3329 messages |
| 2008年07月10日 16:57:09 | Rhamphoryncus | create | |