the originalbut it is located at different address in memory this is true whether the object is unpickled in the same or future process againthe unpickled object is =but is not isc:\pp \dbasepython import pickle open('temp''wb' ['hello'('pickle''world')pickle dump(xff close( open('temp''rb' pickle load(fy ['hello'('pickle''world') =yx is (truefalselist with nested tuple close to flush changes same valuediff objects to make this process simpler stillthe module in example - wraps pickling and unpickling calls in functions that also open the files where the serialized form of the object is stored example - pp \dbase\filepickle py "pickle to/from flat file utilitiesimport pickle def savedbase(filenameobject)"save object to filefile open(filename'wb'pickle dump(objectfilefile close(def loaddbase(filename)"load object from filefile open(filename'rb'object pickle load(filefile close(return object pickle to binary file any file-like object will do unpickle from binary file re-creates object in memory to store and fetch nowsimply call these module functionshere they are in action managing fairly complex structure with multiple references to the same nested object--the nested list called at first is stored only once in the filec:\pp \dbasepython from filepickle import [ {' ': ' ':ltable {' ': ' ':dsavedbase('myfile'table databases and persistence appears twice serialize to file