#21312: models.DateTimeField with default=now: South migration fails
---------------------------------+--------------------------------------
Reporter: magopian | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.6-beta-1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by akaariai):
I've taken a quick look at this. This was introduced by
ddff6522fa72aacc7475ba5cd4bf8683ff12b8c7. The problem is that South
doesn't assign the field to any model. In Django self.model should always
exists (or at least always after app-loading).
I am not sure if this should be fixed in Django or in South. We can
definitely say that South relies on non-public usage of fields (after all
the only public way to use fields is to assign them to models in model
definition, and that means they will have self.model set). OTOH it seems
pretty simple to fix this in Django... I have generally favoured "private
API is private" -approach, so I am slightly in favour of that
interpretation.
--
Ticket URL: <https://code.djangoproject.com/ticket/21312#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.24e315c90e7c38a678aca34f1f704525%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
