--
Ticket URL: <https://code.djangoproject.com/ticket/22109>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* cc: chris.jerdonek@… (added)
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/22109#comment:1>
Comment (by timo):
I'm not quite sure what you are suggesting. Could you given an example or
offer a patch?
--
Ticket URL: <https://code.djangoproject.com/ticket/22109#comment:2>
Comment (by cjerdonek):
I can try to find time to come up with a patch. In the meantime, to say a
little more about what I'm getting at, it turns out that the point I was
trying to raise in this issue is discussed in the Django documentation,
though not in the `STATIC_URL` documentation itself (which is supposed to
contain details about the setting). Namely, the point is discussed
[https://docs.djangoproject.com/en/dev/ref/contrib/staticfiles/ here] in
the "The staticfiles app" section. For example, it says, "This helper
function will only work if `DEBUG` is `True` and your `STATIC_URL` setting
is neither empty nor a full URL such as http://static.example.com/."
In other words, the functionality I'm referencing only becomes enabled
when `STATIC_URL` is a relative URL reference (i.e. does not contain the
host name, etc).
--
Ticket URL: <https://code.djangoproject.com/ticket/22109#comment:3>
* status: new => closed
* resolution: => wontfix
Comment:
The docs for `STATIC_URL` link to the docs for the `staticfiles` app,
which seems reasonable and DRY to me.
There's tons of useful information in the `staticfiles` docs, including
but not limited to this one, and it isn't a good idea to duplicate it.
--
Ticket URL: <https://code.djangoproject.com/ticket/22109#comment:4>