When you run the test.py in attachment, it will print a False but the two enumeration value which are acquired in different ways is same

This issue is not unique to Enum, and is not an Enum problem.

What is happening is that "test.py" has the `__name__` of `__main__` because it is being directly executed from the command line, but when `test2.py` imports it, it is being re-executed and everything inside is re-created -- so you end up with two copies of everything in that module.

You can also see this issue if you manage to import a module under two different names (usually by messing with `sys.path`).

To see it yourself, add a custom __str__ to A:

        def __str__(self):
            return "%s.%s.%s" % (
                    __name__,
                    self.__class__.
                   __qualname__, self._name_,
                   _)

Then your print() will show:

    __main__.A.a test.A.a