#32689: Infinite AlterField Migrations due to default callable object missmatch
-------------------------------------+-------------------------------------
Reporter: Samuel Bishop | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 3.2
Severity: Normal | Resolution:
Keywords: infinite, | Triage Stage:
makemigrations, migrations, | Unreviewed
callable, default, field |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
> 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.
Can you add more details about this callable (an example)? or maybe a
sample project.
--
Ticket URL: <https://code.djangoproject.com/ticket/32689#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.7510b7cf76e10cc9204c6e295675edab%40djangoproject.com.
