#23890: Deprecation warning with numpy 1.8+
--------------------------------------+------------------------------------
     Reporter:  timgraham             |                    Owner:  nobody
         Type:  Cleanup/optimization  |                   Status:  new
    Component:  Template system       |                  Version:  master
     Severity:  Normal                |               Resolution:
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  0                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------

Comment (by timgraham):

 It looks like if the current
 
[https://github.com/django/django/blob/c1552af1fe5832011e3b1c3e5b40c20ff3dbe6f9/django/template/base.py#L763-L767
 string based lookup] fails with any of the caught exceptions `(TypeError,
 AttributeError, KeyError, ValueError, IndexError)`, then we'll fall back
 to trying
 
[https://github.com/django/django/blob/c1552af1fe5832011e3b1c3e5b40c20ff3dbe6f9/django/template/base.py#L778-L779
 integer based lookup] which should work. I'll just silence the deprecation
 warnings in our tests for now.

--
Ticket URL: <https://code.djangoproject.com/ticket/23890#comment:1>
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/067.fe74c38da7b4c8e92a067efd025d2507%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to