#22995: Deprecate auto_now and auto_now_add and document alternatives
-------------------------------------+-------------------------------------
Reporter: jezdez | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.6
Component: Database layer | Resolution:
(models, ORM) | Triage Stage:
Severity: Normal | Unreviewed
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by kmtracey):
I'm not much of a fan of deprecating without removing either as I'm not a
big fan of nanny warnings. If I know what I'm doing, have read the doc and
understand the limitations of what I'm using, I don't really want the code
nagging me that what I'm doing is "unclean". Bleh. Near as I can tell the
straightforward do-it-yourself implementations are going to be equally
vulnerable to gotchas...how is forcing people to try doing it themselves
any better?
For the alternatives proposed: are they going to be immune from the
gotcahs of the existing implementation? If not then why bother?
--
Ticket URL: <https://code.djangoproject.com/ticket/22995#comment:12>
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/064.e7f7e680a362030963304ee18127d4a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
