Tim Peters wrote: > Purely accidental -- nothing guaranteed -- details can (& do) change > across releases. Read obmalloc.c for a tour of the accidents du jour.
cool. thanks for the pointer! > Not true, so be glad to forget it. forget what??? ;-) > A curious possibility: if you do a debug build of Python, obmalloc.c > arranges to overwrite all of an object's memory as soon as the object > is reclaimed (by any means, refcounting or otherwise). That wasn't > for "security" (faux or otherwise), it's to make it easier to detect > buggy C code referencing freed memory. i liked the other Tim's suggestion of a secure string ;-) Les Schaffer -- http://mail.python.org/mailman/listinfo/python-list
