very large project with >100 models, ~30 apps, and it
> still takes less than a second.
>
> On Thursday, October 22, 2015 at 12:15:59 PM UTC+1, Žan Anderle wrote:
>>
>> Adam: I don't think they should be optional, or if they are, they should
>> be opt-out. T
Adam: I don't think they should be optional, or if they are, they should be
opt-out. The checks are a brilliant guard against error, but not running
them as part of test invites them not being run at all in a TDD workflow,
as often code can be developed with nothing but running the tests. It i
Hi folks!
I've been thinking about admindocs lately and that they would really
deserve more attention than they currently get. It's a quite useful feature
and I think a very underrated one.
They were initially there to provide documentation for 'front-end people',
when working on templates. Wh
Luke
>
> On 07/08/15 14:02, Tim Graham wrote:
>
> I guess we might have to wait for Luke to reply to explain the reasoning
> for the original decision.
>
> On Friday, August 7, 2015 at 8:47:23 AM UTC-4, Žan Anderle wrote:
>>
>> That's true. But it still se
on
> that says the view should only be used when DEBUG=True. The default
> template also includes logic to vary the content based on DEBUG.
>
> On Saturday, August 1, 2015 at 11:28:57 AM UTC-4, Žan Anderle wrote:
>>
>> Hey everyone!
>>
>> I noticed today that CS
Hey everyone!
I noticed today that CSRF_FAILURE_VIEW is used even when DEBUG=False. I'm
not sure why this is so and I think it would make much more sense to use
default 403 handling when DEBUG=False.
I checked the ticket where this was initially added, to see if there was a
particular reason f
favour of adding this, possibly just by default not
> hidden. The hidden adds a level of backwards incompatibility which is nice.
>
> Have you opened a ticket for this change? You may also wish to review the
> contributing
> guide <https://docs.djangoproject.com/en/1.8/interna
contrib.admindocs will only document template tags and functions that can
be invoked from templates. Therefore it has limited use. It would be really
useful to be able to document all of the functions in the models (not just
the ones that don't take any arguments). contrib.admindocs is a neat wa
