#21954: 1.7a1 - Migration syntax error ----------------------------+--------------------------------------- Reporter: caulagi | Owner: Type: Bug | Status: new Component: Migrations | Version: 1.7-alpha-1 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 russellm):
* status: closed => new * resolution: invalid => Comment: @loic84 - he may well be advised to use `datetime.now`, but that doesn't change the fact that using ``datetime.now()`` is a valid value for a default. It's an unusual value, to be sure, but it is a *valid* value. Off the top of my head, one possible use case would be to set up a membership model where memberships start Jan 1 2014, unless otherwise specified. -- Ticket URL: <https://code.djangoproject.com/ticket/21954#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/065.7883defdba790a0294e7537d6bd95b31%40djangoproject.com. For more options, visit https://groups.google.com/groups/opt_out.