the current typings still have `__contains__` on the wrong object... we should make sure we are tracing this properly now
the current typings still have
__contains__on the wrong object... we should make sure we are tracing this properly now