Duck-typing would make this somewhat more future-proof, but this is Good Enough given that future refactors will use a subclass of dict here.

If they do use a not-a-dict in the future, if they fail to refactor both these dicts at the same time, and they'd get a failure from this new test in the form of "<strangeobj> != {'foo':'bar', ...}"