#21939 closed Cleanup/optimization (fixed)
Deprecate loading ssi/url tags from future
Reported by: | Tim Graham | Owned by: | Zbigniew Siciarz |
---|---|---|---|
Component: | Template system | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
In #18037, it was decided to add this to the deprecation timeline under 2.0: "ssi
and url
template tags will be removed from the future
template tag library (used during the 1.3/1.4 deprecation period)."
At this time, it appears unlikely (from the discussion I've come across) that Django will have a "2.0" in the sense of a major backwards incompatible release in the foreseeable future. Thus, I think having this on the deprecation timeline may create some confusion. If we want to keep it, I think we should at least add some clarifying text as to what "2.0" means.
Change History (13)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
We might also choose 2.0 as the Django version where we drop Python 2 support.
comment:4 by , 11 years ago
Looking back at the ticket I have to say, I think I still believed that a Django 2.0 would eventually be a API breaking release as Python 3. Now that we know how hostile that has been to Python I think we should reconsider this and use a proper deprecation roadmap.
I also would rather not use those poor template tags for creating a precedence of deciding what 2.0 means -- it's a much bigger discussion and shouldn't bound to bad decisions of the past. Let's move the deprecation into 1.9 and be done with it.
comment:5 by , 11 years ago
Component: | Documentation → Template system |
---|---|
Easy pickings: | set |
Summary: | Reconsider "2.0" deprecation of ssi/url tags from future → Deprecate loading ssi/url tags from future |
Triage Stage: | Unreviewed → Accepted |
@jezdez -- sounds good to me. Should be relatively "easy pickings" by following the deprecating a feature guide.
comment:6 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:7 by , 11 years ago
Owner: | removed |
---|---|
Status: | assigned → new |
comment:8 by , 11 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:9 by , 11 years ago
The note at https://docs.djangoproject.com/en/dev/intro/tutorial03/#removing-hardcoded-urls-in-templates is mentioning Django < 1.5, is it worth keeping it?
comment:10 by , 11 years ago
We can remove that note. The latest version of the tutorial isn't designed to support multiple versions.
comment:12 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I think 2.0 is simply the version after 1.9. Unless someone says otherwise, this is going to happen ;-)