Python 3.14: TypeError: auto(...) is not a string

[noamkush]

With this code:

from django_enum.choices import TextChoices
from enum import auto


class MyTextChoices(TextChoices):
    custom_value: str

    FOO = auto(), "FOO", "foo123"

I get this error

Traceback (most recent call last):
  File "bug.py", line 4, in <module>
    class MyTextChoices(TextChoices):
    ...<2 lines>...
        FOO = auto(), 'FOO', 'foo123'
  File "/home/noam/venv/lib/python3.14/site-packages/django_enum/choices.py", line 37, in __new__
    cls = super().__new__(mcs, classname, bases, classdict, **kwargs)
  File "/home/noam/venv/lib/python3.14/site-packages/enum_properties/__init__.py", line 662, in __new__
    cls = super().__new__(
        mcs,
    ...<3 lines>...
        **kwargs,
    )
  File "/home/noam/venv/lib/python3.14/site-packages/django/db/models/enums.py", line 49, in __new__
    cls = super().__new__(metacls, classname, bases, classdict, **kwds)
  File "/home/noam/.pyenv/versions/3.14.0/lib/python3.14/enum.py", line 549, in __new__
    enum_class = super().__new__(metacls, cls, bases, classdict, **kwds)
  File "/home/noam/.pyenv/versions/3.14.0/lib/python3.14/enum.py", line 255, in __set_name__
    enum_member = enum_class._new_member_(enum_class, *args)
  File "/home/noam/.pyenv/versions/3.14.0/lib/python3.14/enum.py", line 1353, in __new__
    raise TypeError('%r is not a string' % (values[0], ))
TypeError: auto('FOO') is not a string

I think it may be possible that add_member_and_properties doesn't take into account the label.

[bckohan]

Thanks for this report.

In Python 3.14 type hint resolution was made lazy. This required significant upstream changes to enum-properties which now has to defer property resolution until __new__, when before it could happen as members were defined using a custom implementation of the class dictionary. There's something about the interplay between this deferred resolution and the Django Choice meta class that is causing this auto value to slip through unresolved. This should work so I will fix it. I'm not sure if the most appropriate place is here or enum-properties yet.

I do have some suggestions though:

1. It's best to either avoid the use of auto() or to implement _generate_next_value_ if you are going to use it. The primitive value that auto() resolves to may change between python versions or with your enum definition for some types if the member order changes. This means its possible that your code base enum values and database values could become out of sync.
2. django-enum allows you to bypass the Django choice types. You could also implement your enum like this which will work:

from enum_properties import StrEnumProperties
from enum import auto


class MyTextChoices(StrEnumProperties):

    label: str
    custom_value: str

    FOO = auto(), "FOO", "foo123"