Closed justinabrahms closed 8 years ago
This looks fine overall but can you explain what Django is doing that treats named functions differently from lambdas in this case (if you know)?
https://docs.djangoproject.com/en/1.9/ref/models/fields/#default says that lambdas are incompatible with migrations. If you look at the resulting migration, it references it via import, which can't happen if it's a lambda.
Sounds good :+1:
This allows django to serialize it for the purposes of migration generation.