#35335: Update "Enabling the sites framework" documentation to reiterate the
ability to use `get_current_site`
-------------------------------------+-------------------------------------
Reporter: Sam Darwin | Owner: sam
Type: | darwin
Cleanup/optimization | Status: assigned
Component: contrib.sites | Version: 5.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sam Darwin):
> too opinionated, and
> contrasts with the intentional neutrality
In the world of software though, it's often possible that new libraries
are introduced, new features are created, and then the general consensus
is that you ought to tend towards the new method. Meanwhile, the earlier
techniques can pass through phases where they are discouraged, deprecated,
and finally obsolete and not supported at all.
Consider this quote, from a web search:
> The os.system function is easy to use and interpret: simply use as input
of the function the same command you would use in a shell. However, it is
deprecated and it is recommended to use subprocess now.
Is it not true, that `subprocess` is recommended, while `os.system` is
deprecated?
Or that Python 2 is completely unsupported, while the choice of Python 3
is strongly recommended (compared to Python 2) ?
It depends on the method in question. If `get_current_site(request)` is
newer and has more robust features than `get_current()`, then it could be
analogous to `os.system` versus `subprocess`. Certain options actually
can become deprecated and/or recommended. And when that occurs, it isn't
lacking in neutrality to discuss them.
--
Ticket URL: <https://code.djangoproject.com/ticket/35335#comment:2>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018e823b8b93-a3f14fdc-aa9f-44fb-b0f6-b9dac57e334c-000000%40eu-central-1.amazonses.com.
