#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: | master |
| 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)
Changed 10 years ago by
| Attachment: | auto_add.diff added |
|---|
comment:1 Changed 10 years ago by
| Has patch: | set |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:3 Changed 10 years ago by
| Cc: | jedzez added |
|---|
comment:4 Changed 10 years ago by
| 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 Changed 9 years ago by
| Cc: | Jannis Leidel added; jedzez removed |
|---|
Note: See
TracTickets for help on using
tickets.
Raises a deprecation warning