Defining equality for a class without also defining hashability PYL-W1641
Bug risk
Major
5 months ago
—
2 years old
Implementing __eq__ without also implementing __hash__
482 return cls2
483
484
485class ROIExtractionProfile(BaseModel, metaclass=ROIExtractionProfileMeta): # pylint: disable=E1139486 """
487 :ivar str ~.name: name for segmentation profile
488 :ivar str ~.algorithm: Name of algorithmImplementing __eq__ without also implementing __hash__
240AlgorithmType = typing.TypeVar("AlgorithmType", bound=typing.Type[AlgorithmDescribeBase])
241
242
243class Register(typing.Dict, typing.Generic[AlgorithmType]):244 """
245 Dict used for register :class:`.AlgorithmDescribeBase` classes.
246 All registers from `PartSeg.PartSegCore.register` are thisImplementing __eq__ without also implementing __hash__
10
11
12@register_class(old_paths=["PartSeg.utils.mask_create.MaskProperty"])
13class MaskProperty(BaseModel): 14 """
15 Description of creation mask from segmentation
16
Description
In order to conform to the object model, classes that define their own equality method should also define their own hash method, or be unhashable. If the hash method is not defined then the hash of the super class is used. This is unlikely to result in the expected behavior.
A class can be made unhashable by setting its __hash__ attribute to None.
In Python 3, if you define a class-level equality method and omit a __hash__ method then the class is automatically marked as unhashable.
It is recommended to implement a __hash__ method or set __hash__ = None, whenever you define an __eq__ method for a class.