Gregory P. Smith <g...@krypto.org> added the comment:
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. ---------- nosy: +gregory.p.smith resolution: -> rejected stage: -> resolved status: open -> closed type: security -> enhancement versions: +Python 3.10 -Python 3.9 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue43357> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
