I ran into this issue when attempting to add a custom _generate_next_value_ method to an existing Enum. Adding the method definition to the bottom of the class causes it to not be called at all:from enum import Enum, autoclass E(Enum):A = auto()B = auto()def _generate_next_value_(name, *args):return nameE.B.value  # Returns 2, E._generate_next_value_ is not calledclass F(Enum):def _generate_next_value_(name, *args):return nameA = auto()B = auto()F.B.value  # Returns 'B', as intendedI do not believe that the order of method/attribute definition should affect the behavior of the class, or at least it should be mentioned in the documentation.

Immediate solution is to raise an exception if `_generate_next_value_` is defined after members.Possible future solution is to save all member definitions until after class is defined.The exception-raising solution would require a check in `_EnumDict` where `_generate_next_value_` is saved -- if any members already exist, raise.

While the current behavior may be initially unexpected, it does match the way that python normally behaves when defining class variables. For example, the following class will throw an exception because the function number_two() is called before it is defined:class Numbers:    one = 1    two = number_two()    def number_two():        return 2# NameError: name 'number_two' is not definedHowever, this version is fine:class Numbers:    one = 1    def number_two():        return 2    two = number_two()

Jonathan Hsu, you are correct -- and "don't do that" was my initial response; but Enum takes many pains to make sure the user doesn't shoot themselves in the foot, so raising a TypeError is appropriate instead of silently doing the wrong thing.

Thank you for the explanation.

Hi,I have ran the code with with _generate_next_value_ method at the bottom of the class and didn't run into any exceptions. Please refer my python file. Please let me know if I am missing something.from enum import Enum, autoclass E(Enum):A = auto()B = auto()def _generate_next_value_(name, *args):return namefor l in (E):print(l.name)print(l.value)

Ankesh, that is the expected behavior as no patch has been merged yet.

New changesetd9a43e20facdf4ad10186f820601c6580e1baa80 by Ethan Onstott in branch 'master':bpo-40025: Require _generate_next_value_ to be defined before members (GH-19098)https://github.com/python/cpython/commit/d9a43e20facdf4ad10186f820601c6580e1baa80

New changesetb5ecbf02e4dbdea6d1c9a6d7189137f76e70c073 by Miss Islington (bot) in branch '3.8':bpo-40025: Require _generate_next_value_ to be defined before members(GH-19763)https://github.com/python/cpython/commit/b5ecbf02e4dbdea6d1c9a6d7189137f76e70c073

New changesetebd44003c9e206755e5e28716242ed8941495a62 by Miss Islington (bot) in branch '3.7':bpo-40025: Require _generate_next_value_ to be defined before members (GH-19762)https://github.com/python/cpython/commit/ebd44003c9e206755e5e28716242ed8941495a62

We can close this?

Not yet.  I want to investigate the idea Ankesh Saha had some more.

There was an effort to make it so `_generate_next_value_` could be defined last and still work correctly -- unfortunately, it could not handle the more common case of using `auto()` with the default `_generate_next_value_`:  class I(Enum):      first = auto()      second = first + 2    # this line would failClosing the ticket.  Thank you everyone!