Hi,
I have a patch for #11930 that in to be applied against djangoproject.com's
base.css file. As far as I can see, base.css is not in the project
repository. Who is the custodian of this file, and the other CSS files? Is
there a reason it's not in the repo?
Greg.
--
Dr Greg Turner
Director, t
My personal preference is for (4). I don't like the addition of a
setting, but it's a setting that most users will be able to ignore
(since there is a reasonably sensible default), and it is the most
explicit and configurable option available.
My opinion with the current codebase is for (4), b
On 04/12/10 09:15, Tim Diggins wrote:
View& template:
look for a handle{{status_code}} variable, falling back to
handle_exception. The generic handle_exception in non-DEBUG looks for
a specific "{{status_code}}.html" template, but falls back to a (say)
"http_exception.html" template. (there woul
On 03/12/10 22:50, Russell Keith-Magee wrote:
This proposal has come up before and has historically been rejected;
however, your point about class-based views makes it a lot harder to
give the standard responses.
Yup; this email came directly from using the new CBVs and hitting this
very probl
(and apologies, (just after I hit send) I realized that I may be off
mark, as I'm not working with 1.3/dev in my current apps... so I may
be missing some critical changes in 1.3.)
On Dec 4, 9:15 am, Tim Diggins wrote:
> This sounds good to me, but can I give an additional or alternative
> excepti
This sounds good to me, but can I give an additional or alternative
exception handling, for consideration (feels a bit simpler, both to
use and to implement):
Exceptions:
When catching an exception in BaseHandler.get_response look for a
"status_code" attribute (getattr(e, 'status_code', 500)) then
