为什么在腌制后在Python isinstance中出现意外行为?


问题内容

撇开isinstance的使用是否有害,我在通过Pickle对对象进行序列化/反序列化后尝试评估isinstance时遇到了以下难题:

from __future__ import with_statement
import pickle

# Simple class definition
class myclass(object):
    def __init__(self, data):
        self.data = data

# Create an instance of the class
x = myclass(100)

# Pickle the instance to a file
with open("c:\\pickletest.dat", "wb") as f:
    pickle.dump(x, f)

# Replace class with exact same definition
class myclass(object):
    def __init__(self, data):
        self.data = data

# Read an object from the pickled file
with open("c:\\pickletest.dat", "rb") as f:
    x2 = pickle.load(f)

# The class names appear to match
print x.__class__
print x2.__class__

# Uh oh, this fails...(why?)
assert isinstance(x2, x.__class__)

谁能阐明为什么ininstance在这种情况下会失败?换句话说,Python为什么认为这些对象属于两个不同的类?当我删除第二个类定义时,isinstance工作正常。


问题答案:

这是取消选取程序的工作方式(site-packages / pickle.py):

def find_class(self, module, name):
    # Subclasses may override this
    __import__(module)
    mod = sys.modules[module]
    klass = getattr(mod, name)
    return klass

查找并实例化一个类。

因此,当然,如果将一个类替换为一个具有相同名称的类,则klass = getattr(mod, name)将会返回新类,并且该实例将属于该新类,因此isinstance将失败。