Add blurb about included enumeration types in Django 3.0? about django-enumfields

[johnthagen]

As noted at the bottom of https://stackoverflow.com/a/58051918, one (in my view big) differences between Django's native enumeration types and django-enumfield is that Django's returns a str when accessed rather than the actual Enum instance.

That means you can do the following in django-enumfields but not with Django Choices:

if my_model.color is Color.Red:
    ...

which is the preferred way to do type-safe Enum evaluation in Python.

With Django Choices you'd need to do something like:

if Color[my_model.color] is Color.Red:
    ...

or create a helper method for each Enum field to do this.

[jalaziz]

Looking at the code, it seems like this package would actually work just fine with Django's enumeration types. About to test it out, but it might be good to provide examples that use Django's Choices class and its subclasses.

[johnthagen]

Something I didn't realize the first time I read about the new Django 3.0+ enumeration types is that they are in fact "real" Python enums.

If you look at the Django source code:

class ChoicesMeta(enum.EnumMeta):
    """A metaclass for creating a enum choices."""

...

class Choices(enum.Enum, metaclass=ChoicesMeta):
    """Class for creating enumerated choices."""

They are really just Enums with some extra methods added onto them. My hesitation with using them when I first read about them is that it wasn't clear that they are truly Python Enums, so I preferred to stay with this package. But now that I know they are true Enums (not something that is totally Django-specific other than a few helper methods) I'm planning to move to them.

I hope this helps others who might have had a similar concern.

[johnthagen]

I created a Django issue related to improving the docs in this area: https://code.djangoproject.com/ticket/33193