#21939: Reconsider "2.0" deprecation of ssi/url tags from future
-------------------------------------+-------------------------------------
     Reporter:  timo                 |                    Owner:  nobody
         Type:                       |                   Status:  new
  Cleanup/optimization               |                  Version:  master
    Component:  Documentation        |               Resolution:
     Severity:  Normal               |             Triage Stage:
     Keywords:                       |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

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>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.0f851a90d31bbbd5791ee91414619132%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to