Hi Marc,
fine, was thinking on supporting just the simple case without the Prefetch
object.
Il 31/12/2015 00:30, Marc Tamlyn ha scritto:
Hi Richard,
Overriding the queryset is a pretty simple method override, I'm not sure there
is sufficient need for prefetching here. In particular, the synta
> On 29 Dec 2015, at 01:36, Tim Graham wrote:
>
> I'd like to work together with Dave to develop a proof of concept that
> integrates whitenoise into Django. I spent about an hour looking through
> whitenoise and our own static file serving code, and I think integrating
> whitenoise will yiel
In my opinion one of the most important goals for Django is to make
deploying tiny projects securely and easily a trivial matter. We
aren't there right now.
If you have a site where traffic is less than one hit per minute, you
shouldn't care about performance that much.
With Django, it is pretty
>>Anything that improves the development experience for tiny sites gets
>>a big +1 from me.
As a solo developer that usualy deploy a diferent application every 3 weeks
or so, cant agree more.
Big +1 for me too.
--
You received this message because you are subscribed to the Google Groups
"Djang
2015-12-31 12:52 GMT+01:00 Anssi Kääriäinen :
> In my opinion one of the most important goals for Django is to make
> deploying tiny projects securely and easily a trivial matter. We
> aren't there right now.
>
+1
I'm maintaining three such sites (my wife's, my consultancy's and mine). I'm
clear
On Wednesday 30 December 2015 08:40:17 martin f krafft wrote:
> also sprach Shai Berger [2015-12-10 08:38 +1300]:
> > As far as I can see, you are trying to implement it in the model,
> > rather than as a new kind of field. Try to write
> > ExtendedGenericForeignKey, and I think things would look
Hi All,
tldr: I think we should keep django.core.urlresolvers forever, or at least
much much longer. Moving things to django.core.urls makes sense; removing
the one line import shim from django.core.urlresolvers doesn't make sense
to me.
General thoughts about compatibility, using this situati
I'm still +1 to django providing a good file solution, whether it be
whitenoise, dj-static, or whatever.
Here's all I came up with the last time I looked into this. It basically
involves passing insecure=True into our current code and sending cache
headers. (I feel like the insecure flag could
A question: are there any plans to also improve MEDIA files (user uploaded
files) in any foreseeable future?
Perhaps this is outside the scope of Django, but I believe Django could
provide by default, any option to get a little more control over who can
and can not access the MEDIA files.
Most
