#25830: Unnecessary migrations with Python3
----------------------------+--------------------------------------
Reporter: bronger | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Changes (by aaugustin):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
This may be because the definition of models changes every time you run
the project e.g. using `default=timezone.now()` instead of
`default=timezone.now` will trigger this behavior.
Can you provide one of the migrations? This will make it easier to see
what changes and whether it's a bug in your code or in Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/25830#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.74fc434088f43204d62bd16cadf06b03%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
