#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 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
I was marking this accepted by what dstufft says in comment:12 - it seems
we have deprecated features even if it would not be necessary for
technical reasons.
There is a lot of point in not deprecating stuff, too. We don't have long
term releases, and any deprecation is at least a minor burden for those
upgrading from older versions of Django. Users are forced to do those
upgrades if they want security updates directly from Django.
If we want to cause less pain for upgrades, then how about
user.get_profile() deprecation? I don't see that as something we must
absolutely do, and it is going to cause even more pain than deprecation of
permalink.
I am not +/- anything on deprecation of user.get_profile() or permalink as
individual items. In general, I am in favour of deprecating less stuff.
But, we should be consistent in how we deprecate stuff.
I am kind of liking deprecating stuff but not removing it after two
releases. That is, we should have a longer deprecation period for API
purity deprecations.
--
Ticket URL: <https://code.djangoproject.com/ticket/18974#comment:14>
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.
