#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 kmtracey):
Replying to [comment:16 dstufft]:
> However I think we're likely just going back and forth here, I'm unsure
of what the next step would be, how do we get a decision made so we can
either get this deprecated or get the docs fixed?
Start by giving it some time for more people to notice this ticket and
chime in with an opinion -- this ticket is only 2 days old. I agree with
Russell on this one, I think formal deprecation of permalink will cause
more pain than it is worth. I'd start by changing docs to discourage use
and point people in the right direction, possibly noting that permalink
may be formally deprecated at some point in the future. I don't see the
anti-pattern argument as compelling for this one as for `import *`.
Imports are are fundamental concept that newbies have to learn, decorators
not so much. Newbies to Python generally aren't going to start writing
their own decorators based on experience with a single decorator present
in Django, whereas if `import *` is present in Django's tutorial they
certainly may pick up that bad habit.
--
Ticket URL: <https://code.djangoproject.com/ticket/18974#comment:17>
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.