Changes between Version 1 and Version 2 of Ticket #32689
- Timestamp:
- Apr 27, 2021, 11:05:43 PM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #32689 – Description
v1 v2 6 6 7 7 I would have expected either a clear warning detailing why my choice of callable object for the `default=` will cause issues, or I would have expected `makemigrations` to not mutate my callable like this. 8 9 Root cause: Turns out this is a serialisation fault. The migration serialiser doesn't throw any kind of error or warning and just mutates the callable instead of preventing me from using an invalid default callable that the migration framework wont be able to serialise. A simple wrapper function added to the custom field library solves the matter entirely, however the underlying issue of the migration framework behaviour is worth looking at improving.