We're deprecating SopelMemory.contains() in version 7, and the actual example code already uses the in operator instead. in uses the magic __contains__() method, which is exactly what contains() calls, so… There's literally no difference. This should have been done a LONG time ago, like before the name change to Sopel (contains() has been a mere wrapper for __contains__() for nearly six years already). In fact, this can probably go on the live website whenever, without waiting for Sopel 7 to drop.
We're deprecating
SopelMemory.contains()
in version 7, and the actual example code already uses thein
operator instead.in
uses the magic__contains__()
method, which is exactly whatcontains()
calls, so… There's literally no difference. This should have been done a LONG time ago, like before the name change to Sopel (contains()
has been a mere wrapper for__contains__()
for nearly six years already). In fact, this can probably go on the live website whenever, without waiting for Sopel 7 to drop.