What I usually do is add an abstract method to my item base class which is i.e. called is_usable and receives someobject. This method overriden in the different item subclasses then decide upon this item can be used onto something else, like another item, an enemy, a tile, the player, whatsoever. A pythonic example could look like the following:

from abc import ABC

class item(ABC):

  @abstractmethod
  def is_usable(self, obj):
    return False

class dagger(item):
  def is_usable(self, obj):
    if isinstance(obj, player):
      return True # daggers should only be usable on players, nothing else

    return False

I don't have to create lists of multiple objects that way (those could actually create problems with garbage collection due to possible circular references etc), but instead update my is_usable() checks each time something changes. Whereas you could enhance that methods that much so that you don't need to update those alot, like create a weapon class which inherits item and is further derived by e.g. a dagger, a pistol or whatsoever and check on those weapon subclasses to see if any weapon works with a given item. There are so many possibilities to solve your problem, as always . It always depends on your situation.
Best Regards.
Hijacker