➜

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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, loewis, nqiang
Date 2010-10-05.21:32:09
SpamBayes Score 1.4554187e-05
Marked as misclassified No
Message-id <1286314331.09.0.973000000347.issue4872@psf.upfronthosting.co.za>
In-reply-to
Content 
- The "memory leaks" are reported in the IDE output window when the process exits; this lists all non deallocated blocks of memory.  This feature is not enabled by default.  Creating a CString probably initializes this feature.

- Py_Finalize() doesn't free all memory used by Py_Initialize(); this is not a problem, as long as a second call to Py_Initialize() reuses the same memory.

Closing as "won't fix": there is no need to free everything when the process exits.
History
Date User Action Args
2010-10-05 21:32:11amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, loewis, nqiang
2010-10-05 21:32:11amaury.forgeotdarcsetmessageid: <1286314331.09.0.973000000347.issue4872@psf.upfronthosting.co.za>
2010-10-05 21:32:09amaury.forgeotdarclinkissue4872 messages
2010-10-05 21:32:09amaury.forgeotdarccreate