#21905: Add check for default=now() on Date/Time/DateTimeFields
------------------------------+---------------------------------------
Reporter: taishi@… | Owner: nobody
Type: New feature | Status: new
Component: Core (Other) | Version: 1.7-alpha-1
Severity: Normal | Resolution:
Keywords: check | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+---------------------------------------
Changes (by MarkusH):
* keywords: migrate, migrations, datetime => check
* owner: => nobody
* component: Migrations => Core (Other)
Comment:
Given the confusion about passing `default` a `datetime` object instead of
a callable (which solves the problem), I'd like to propose the idea to add
a check to Django's check framework to make users aware of these problems
that might occur over the time when using `datetime.now()` instead of
`datetime.now`.
--
Ticket URL: <https://code.djangoproject.com/ticket/21905#comment:4>
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/083.bbdd387f3a3aac9e1cfdebfd346a9a62%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
