Fixed #25185 -- Added support for functools.partial serialization in migrations

2 files changed, 8 insertions, 0 deletions

diff --git a/docs/releases/1.9.txt b/docs/releases/1.9.txt
index b7863bab03..b14a4040d8 100644
--- a/docs/releases/1.9.txt
+++ b/docs/releases/1.9.txt
@@ -385,6 +385,8 @@ Migrations
   :djadminopt:`migrate --fake-initial <--fake-initial>` to more easily detect
   initial migrations.
 
+* Added support for serialization of ``functools.partial`` objects.
+
 Models
 ^^^^^^
 
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index f979030fb3..c656e56db5 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -652,11 +652,17 @@ Django can serialize the following:
 - ``datetime.date``, ``datetime.time``, and ``datetime.datetime`` instances
   (include those that are timezone-aware)
 - ``decimal.Decimal`` instances
+- ``functools.partial`` instances which have serializable ``func``, ``args``,
+  and ``keywords`` values.
 - Any Django field
 - Any function or method reference (e.g. ``datetime.datetime.today``) (must be in module's top-level scope)
 - Any class reference (must be in module's top-level scope)
 - Anything with a custom ``deconstruct()`` method (:ref:`see below <custom-deconstruct-method>`)
 
+.. versionchanged:: 1.9
+
+    Serialization support for `functools.partial` was added.
+
 Django can serialize the following on Python 3 only:
 
 - Unbound methods used from within the class body (see below)