#18974: Deprecate models.permalink
-------------------------------------+-------------------------------------
Reporter: dstufft | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Design
Severity: Normal | decision needed
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by russellm):
* stage: Ready for checkin => Design decision needed
Comment:
Yeah... I'm gonna weigh in on that :-)
I'm in complete agreement that models.permalink doesn't behave as a good
decorator. However, it's also pretty well entrenched in Django usage.
I'd be pained to remove it purely as part of some sort of move to "API
purity". It's going to force a lot of code churn on a *lot* of projects,
with no real benefit.
Removing examples from the docs? Sure. Annotating the docs to say "This
probably isn't the best way to do reversal"? Sure. But fully deprecating
-- that seems like overkill to me.
Now, if there were to be some sort of greater benefit from this
deprecation -- say, finally getting a resolution to the
[https://code.djangoproject.com/wiki/ReplacingGetAbsoluteUrl Replacing
get_absolute_url proposal], then I might be convinced otherwise.
--
Ticket URL: <https://code.djangoproject.com/ticket/18974#comment:11>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
