#32689: Infinite AlterField Migrations due to default callable object missmatch
-------------------------------------+-------------------------------------
Reporter: Samuel Bishop | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 3.2
Severity: Normal | Resolution: invalid
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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
I don't think there is anything we can improve in Django. `new` is a
different object each time it's imported, so Django properly detects this
as change.
--
Ticket URL: <https://code.djangoproject.com/ticket/32689#comment:5>
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.6bc16ede3b727b77d5d6d59a52d37cb7%40djangoproject.com.
