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 gregory.p.smith
Recipients absvsb, gregory.p.smith
Date 2021-03-13.10:18:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
CPython itself doesn't have guaranteed way to do this kind of thing.  There is no tracking of which types clear memory let alone which API calls may make copies of data in places within their C that are not explicitly cleared afterwards.  We do not have a plan to implement this.

For data that MUST NOT remain in memory in any form anywhere as soon as code is done with it, the best thing to do is isolate all code inputting, processing, and clearing that within the confines of a lower level extension module or a short lived subprocess.
Date User Action Args
2021-03-13 10:18:28gregory.p.smithsetrecipients: + gregory.p.smith, absvsb
2021-03-13 10:18:28gregory.p.smithsetmessageid: <>
2021-03-13 10:18:28gregory.p.smithlinkissue43357 messages
2021-03-13 10:18:28gregory.p.smithcreate