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.
--
Ticket URL: <https://code.djangoproject.com/ticket/21939>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by aaugustin):
I think 2.0 is simply the version after 1.9. Unless someone says
otherwise, this is going to happen ;-)
--
Ticket URL: <https://code.djangoproject.com/ticket/21939#comment:1>
Comment (by claudep):
We might also choose 2.0 as the Django version where we drop Python 2
support.
--
Ticket URL: <https://code.djangoproject.com/ticket/21939#comment:2>
Comment (by aaugustin):
There would be no 1.9 then ;-)
--
Ticket URL: <https://code.djangoproject.com/ticket/21939#comment:3>
Comment (by jezdez):
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/21939#comment:4>
* component: Documentation => Template system
* easy: 0 => 1
* stage: Unreviewed => Accepted
Comment:
@jezdez -- sounds good to me. Should be relatively "easy pickings" by
following the
[https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
/submitting-patches/#deprecating-a-feature deprecating a feature] guide.
--
Ticket URL: <https://code.djangoproject.com/ticket/21939#comment:5>
* owner: nobody => zsiciarz
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/21939#comment:6>
* status: assigned => new
* owner: zsiciarz =>
--
Ticket URL: <https://code.djangoproject.com/ticket/21939#comment:7>
* status: new => assigned
* owner: => zsiciarz
--
Ticket URL: <https://code.djangoproject.com/ticket/21939#comment:8>
Comment (by zsiciarz):
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?
--
Ticket URL: <https://code.djangoproject.com/ticket/21939#comment:9>
Comment (by timo):
We can remove that note. The latest version of the tutorial isn't designed
to support multiple versions.
--
Ticket URL: <https://code.djangoproject.com/ticket/21939#comment:10>
Comment (by zsiciarz):
Deprecated, relevant PR: https://github.com/django/django/pull/2308
--
Ticket URL: <https://code.djangoproject.com/ticket/21939#comment:11>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"74d4d58b62f3a68bf77b983bc8a475a130d1f95e"]:
{{{
#!CommitTicketReference repository=""
revision="74d4d58b62f3a68bf77b983bc8a475a130d1f95e"
Fixed #21939 -- Deprecated loading ssi/url tags from future.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21939#comment:12>
Comment (by Tim Graham <timograham@…>):
In [changeset:"bd93032191f96bc7086aa46b91b4177601c6fce9"]:
{{{
#!CommitTicketReference repository=""
revision="bd93032191f96bc7086aa46b91b4177601c6fce9"
Removed ssi/url tags from future per deprecation timeline; refs #21939.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21939#comment:13>