#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
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* component: Uncategorized => Core (Other)
* stage: Unreviewed => Accepted
Comment:
Hey William.
OK, let's accept this, but can I ask you to (briefly) write up a "Roadmap
to Freezable Django", perhaps just for the mailing list, rather than a
full DEP (but do use the DEP template if that helps)?
You've obviously got an end goal in mind — and that's probably worthwhile
and something we should have in mind as a target — but these sequence of
little adjustments feel a bit like death-by-a-thousand-cuts (if that makes
sense). No problem with them, but the overview, and the obstacles
currently foreseeable would be good to discuss, and to get wise-folk input
on.
Make sense? 🙂
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/32316#comment:5>
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.f940b364e1b682c3f0b78ad2d256c259%40djangoproject.com.
