#32316: Access __file__ lazily rather than at module level
-------------------------------------+-------------------------------------
Reporter: William Schwartz | Owner: William
Type: | Schwartz
Cleanup/optimization | Status: assigned
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: freezers | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by William Schwartz):
Yes, I will absolute write a broader memo to the mailing list. It is not
my intention to wear down y'all maintainers!
My plan all along has been to get this and a couple other tickets (#32302
and #32317 in particular) taken care of before the 3.2 feature freeze on
the 14th, experiment with the results for awhile and consult my
colleagues, and then write up something more big-picture for the mailing
list. (I'll check out the DEP template—thanks for the idea.) While I have
an idea of what I want to propose, getting some practical experience with
a frozen, Django project seems prudent before moving beyond minor
cleanups. Besides, my time is extremely constrained at the moment, so
it'll be several weeks before I can write up anything anyway.
Thanks for continuing to work with me on these incremental changes in the
meantime!
--
Ticket URL: <https://code.djangoproject.com/ticket/32316#comment:6>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.b88a4ab03dadcee64c86f9c390ef3916%40djangoproject.com.
