Opened 10 years ago

Closed 10 years ago

Last modified 9 years ago

#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 Aymeric Augustin, 10 years ago

I think 2.0 is simply the version after 1.9. Unless someone says otherwise, this is going to happen ;-)

comment:2 by Claude Paroz, 10 years ago

We might also choose 2.0 as the Django version where we drop Python 2 support.

comment:3 by Aymeric Augustin, 10 years ago

There would be no 1.9 then ;-)

comment:4 by Jannis Leidel, 10 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 Tim Graham, 10 years ago

Component: DocumentationTemplate system
Easy pickings: set
Summary: Reconsider "2.0" deprecation of ssi/url tags from futureDeprecate loading ssi/url tags from future
Triage Stage: UnreviewedAccepted

@jezdez -- sounds good to me. Should be relatively "easy pickings" by following the deprecating a feature guide.

comment:6 by Zbigniew Siciarz, 10 years ago

Owner: changed from nobody to Zbigniew Siciarz
Status: newassigned

comment:7 by Zbigniew Siciarz, 10 years ago

Owner: Zbigniew Siciarz removed
Status: assignednew

comment:8 by Zbigniew Siciarz, 10 years ago

Owner: set to Zbigniew Siciarz
Status: newassigned

comment:9 by Zbigniew Siciarz, 10 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 Tim Graham, 10 years ago

We can remove that note. The latest version of the tutorial isn't designed to support multiple versions.

comment:11 by Zbigniew Siciarz, 10 years ago

comment:12 by Zbigniew Siciarz <antyqjon@…>, 10 years ago

Resolution: fixed
Status: assignedclosed

In 74d4d58b62f3a68bf77b983bc8a475a130d1f95e:

Fixed #21939 -- Deprecated loading ssi/url tags from future.

comment:13 by Tim Graham <timograham@…>, 9 years ago

In bd93032191f96bc7086aa46b91b4177601c6fce9:

Removed ssi/url tags from future per deprecation timeline; refs #21939.

Note: See TracTickets for help on using tickets.
Back to Top