#32316: Access __file__ lazily rather than at module level
-------------------------------------+-------------------------------------
     Reporter:  William Schwartz     |                    Owner:  William
         Type:                       |  Schwartz
  Cleanup/optimization               |                   Status:  assigned
    Component:  Uncategorized        |                  Version:  master
     Severity:  Normal               |               Resolution:
     Keywords:  freezers             |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Tom Forbes):

 I think this makes sense as `__file__` is indeed documented as being
 optional (which is somewhat surprising). If we do go forward with this,
 how do we catch future uses of `__file__` at the module level?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32316#comment:2>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.fcfc7b2abc44bfa250f04a842e48a0ac%40djangoproject.com.

Reply via email to