fix missing import

Author: bckohan

django_enum/forms.py

@@ -116,11 +116,11 @@ def _coerce(self, value: Any) -> Union[Choices, Any]:
         Attempt conversion of value to an enumeration value and return it
         if successful.
 
-        :param value The value to convert
-        :return An enumeration value or the canonical empty value if value is
+        :param value: The value to convert
+        :raises ValidationError: if a valid return value cannot be determined.
+        :return: An enumeration value or the canonical empty value if value is
             one of our empty_values, or the value itself if this is a
             non-strict field and the value is of a matching primitive type
-        :raises ValidationError if a valid return value cannot be determined.
         """
 
         if value in self.empty_values:

django_enum/tests/tests.py

@@ -12,6 +12,7 @@
 from django.test import Client, TestCase
 from django.urls import reverse
 from django_enum import TextChoices
+from django_enum.forms import EnumChoiceField
 from django_enum.tests.djenum.enums import (
     BigIntEnum,
     BigPosIntEnum,

doc/source/usage.rst

@@ -64,7 +64,8 @@ data where no ``Enum`` type coercion is possible.
 
 Setting this parameter to ``False`` will turn off the automatic conversion to
 the field's ``Enum`` type while leaving all validation checks in place. It will
-still be possible to set the field directly as an ``Enum`` instance:
+still be possible to set the field directly as an ``Enum`` instance and to
+filter by ``Enum`` instance or any symmetric value:
 
 .. code-block:: python
 
@@ -154,6 +155,7 @@ Filtering
 #########
 
 
+
 Migrations
 ##########
 
@@ -179,19 +181,13 @@ Performance
 The cost to resolve a raw database value into an ``Enum`` type object is
 non-zero. ``EnumFields`` may not be appropriate for use cases at the edge of
 critical performance boundaries, but for most scenarios the cost of using
-``EnumFields`` will be negligible.
+``EnumFields`` is negligible.
 
 An effort is made to characterize and monitor the performance penalty of
 using ``EnumFields`` over a Django_ native field with choices and integration
 tests assure performance of future releases will not worsen.
 
-For model object creation ``EnumFields`` tend to be about 10% slower than an
-equivalent field with choices and for model object iteration ``EnumFields``
-tend to be about 50% slower.
-
-..
-    .. note::
-
-        The performance penalty can be eliminated by setting ``coerce`` to
-        ``False``.
+.. note::
 
+    The read performance penalty can be eliminated by setting ``coerce`` to
+    ``False``.