Importing a file with relative path and the same file with path from interpreter root creates Enums with different ids.

[feature-engineer]

Bug report

Bug description:

The type of path used to import an Enum affects whether it equals itself or not.

Assume we have a tests directory in our project, and in it are enums1.py and test_enums.py

enums1.py:

import enum


class Color(enum.Enum):
    RED = 1
    GREEN = 2
    BLUE = 3

tests_enums.py:

import enums1
import tests.enums1

d1 = {c: c.name for c in enums1.Color}
print(id(enums1.Color.RED))
print(id(tests.enums1.Color.RED))
print(enums1.Color.RED == tests.enums1.Color.RED)
print(d1[tests.enums1.Color.RED])

running test_enums.py results in two distrinct ids for Color.Red, it says enums1.Color.RED does not equal tests.enums1.Color.RED, and there's a KeyError on the final line.

Expected behavior:
The import path should not affect whether the same enum is equal to itself. there should have been two identical ids, Color.RED should equal Color.RED and there should not be a KeyError.

CPython versions tested on:

3.12

Operating systems tested on:

Linux

[picnixz]

Just to confirm but are the two modules the same? if not, then it's normal that the two objects are different. Namely if enums1 != tests.enums1 then their content won't be the same.

I don't have a way to confirm this but I suspect that this is because we have two different imported objects, though it might actually be the expected behaviour of imports.

[serhiy-storchaka]

It is not the same module and not the same class. The bug is in the user code.

[brettcannon]

I agree with @serhiy-storchaka that this isn't a bug. Enums don't do equality by name, and so having different classes in separate modules means they won't compare equal. If you want to do comparison by name I would get the string of the name and compare that.