My suggestion would be that names starting with a colon ':' (e.g. empty
string as first level namespace) implies current_app if present.
A very simple 2-line solution can be found
[https://github.com/CVi/django/commit/c501c522edebec5fc4d2312c6ec8f7a50fa8ddcd
on my github page]
The question is if this breaches any philosophies of Django. There's no
reason for me to create an elaborate patch including additional tests for
this, if it's going to be cut down for political/design reasons. Therefore
I am not ticking "has patch" just yet.
The possible use-cases for this is template reuse and making applications
modular by simply splitting them up. (my use case covers both)
--
Ticket URL: <https://code.djangoproject.com/ticket/22737>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Design decisions are usually made on the
[https://groups.google.com/forum/#!forum/django-developers django-
developers mailling list]. I would post this idea there to get feedback.
--
Ticket URL: <https://code.djangoproject.com/ticket/22737#comment:1>
* status: new => closed
* resolution: => needsinfo
Comment:
Closing as "needs info" until the discussion happens.
--
Ticket URL: <https://code.djangoproject.com/ticket/22737#comment:2>