#27648: Deprecate ("iLmsu") regex groups in URLpatterns
-------------------------------------+-------------------------------------
               Reporter:  Tim        |          Owner:  Tim Graham
  Graham                             |
                   Type:             |         Status:  assigned
  Cleanup/optimization               |
              Component:  Core       |        Version:  master
  (URLs)                             |
               Severity:  Normal     |       Keywords:
           Triage Stage:  Accepted   |      Has patch:  0
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  0
                  UI/UX:  0          |
-------------------------------------+-------------------------------------
 As [https://groups.google.com/d/topic/django-
 developers/Y51CKkqq6Ng/discussion discussed on django-developers], Python
 deprecated usage of flags not at the start of a regular expression, e.g.
 'CaseInsensitive(?i)' instead of '(?i)CaseInsensitive'. A new solution
 would be required to support these flags in Django, however, since case-
 insensitive URLs aren't a good practice and the other flags don't have
 value in urlpatterns, support for this will be removed. An alternative
 solution for those wanting the functionality is to write a 404 handler to
 look for uppercase characters and redirect to a lowercase equivalent.

--
Ticket URL: <https://code.djangoproject.com/ticket/27648>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.2d775b305b90d95629fbc6664a965810%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to