#7634 closed (wontfix)
Using auto_now or auto_now_add should raise a DeprecationWarning
Reported by: | Alex Gaynor | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | dev |
Severity: | Keywords: | ||
Cc: | Jannis Leidel | Triage Stage: | Accepted |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
To my understanding these are both slated for eventual removal in favor of the default kwarg and overiding the save() method, therefore they should raise a DeprecationWarning to alert people of this fact.
Attachments (1)
Change History (6)
by , 16 years ago
Attachment: | auto_add.diff added |
---|
comment:1 by , 16 years ago
Has patch: | set |
---|---|
Triage Stage: | Unreviewed → Accepted |
comment:3 by , 16 years ago
Cc: | added |
---|
comment:4 by , 16 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
For better or worse, these features are in 1.0 and so aren't going away in the near future.
comment:5 by , 15 years ago
Cc: | added; removed |
---|
Note:
See TracTickets
for help on using tickets.
Raises a deprecation warning