On Aug 15, 1:15 pm, Yuri Baburov wrote:
> Hi all,
>
> I'm trying to figure out correct overall and settings path usage
> strategy for my Django applications.
> What I am experiencing now is that settings.py is imported 4 times on
> "python manage.py runserver" command,
> twice as "settings", an
Hi all,
I'm trying to figure out correct overall and settings path usage
strategy for my Django applications.
What I am experiencing now is that settings.py is imported 4 times on
"python manage.py runserver" command,
twice as "settings", and twice as "myapp.settings", given that my
project is na
Russell Keith-Magee wrote:
> On Sat, Aug 15, 2009 at 8:09 AM, hcarvalhoalves
> wrote:
>> On Aug 13, 9:30 am, Russell Keith-Magee
>> wrote:
>>> On Thu, Aug 13, 2009 at 12:04 AM, Michael Glassford
>>> wrote:
>>>
>>> Secondly: I'm sensitive to the extent that 'on delete cascade' et al
>>> are phra
On Sat, Aug 15, 2009 at 8:09 AM, hcarvalhoalves wrote:
>
> On Aug 13, 9:30 am, Russell Keith-Magee
> wrote:
>> On Thu, Aug 13, 2009 at 12:04 AM, Michael Glassford
>> wrote:
>>
>> Secondly: I'm sensitive to the extent that 'on delete cascade' et al
>> are phrased in SQL specific terms. I fully ac
On Aug 11, 7:50 am, Richard Davies
wrote:
> Hi all,
>
> With 1.1 out of the door (great!), here's a thought for 1.2...
>
> I often end up writing the same couple of template tags and filters. I
> think some of these are general enough and useful enough that they
> should be considered for basic D
On Aug 15, 3:19 am, ccahoon wrote:
> This is the case, yes, if the HTTP and GZip middleware are not used.
> We had to modify both of those to make sure they didn't consume the
> content generator to find the Content-Length. I imagine, IF we wanted
> to, setting the Content-Length header could be
On Aug 13, 9:30 am, Russell Keith-Magee
wrote:
> On Thu, Aug 13, 2009 at 12:04 AM, Michael Glassford
> wrote:
>
> Secondly: I'm sensitive to the extent that 'on delete cascade' et al
> are phrased in SQL specific terms. I fully acknowledge the use case -
> what happens to a FK when the object it
I'm in agreement with Tai. Keeping them separate gives them consistent
behavior for view authors to expect.
"One thing I'm curious about here is the HTTP Content-Length header.
It's late and I'm tired and cranky, so I may have missed it, but
outside of the infrastructure for runserver I can't fin
Currently, we can override the queryset used by ModelAdmins. This is
helpful, since often times the default manager omits instances that
nevertheless belong in the admin. It seems to me that there's no way
to override the queryset for inlines, though. Is that correct?
Inlines seem to use the de
I think I prefer keeping HttpResponse and HttpResponseStreaming
separate. Using the latter indicates explicitly that the user wants to
send a streaming response and disable any middleware that doesn't
explicitly support it. Using the former should always consume any
content passed to it so that mi
On Fri, Aug 14, 2009 at 3:13 AM, ccahoon wrote:
> One bit of advice I am looking for is what people's opinions are on
> the use of isinstance versus hasattr to determine functionality. I am
> personally partial to hasattr, because it covers subclasses, but I do
> not know what the community tends
My last task before the GSoC hard pencils down date on Monday is an
attempt at a solution to ticket #7581. The essential issue is that a
lot of middleware requires access to the whole of
HttpResponse.content, but this prevents streaming responses (to
prevent timeouts).
To allow for streaming resp
12 matches
Mail list logo
