Re: Support byte range requests in django.views.static.serve

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I'd be +1 on doing this -- I know we've always said that Django's static serve isn't for production use, but as video and audio are increasingly common on the web, Django should support them seemlessly. Alex PS: I'm of course open to other ways of

Re: Support byte range requests in django.views.static.serve

On Mon, Apr 14, 2014 at 11:30 AM, wrote: > Is the Django community interested in supporting HTTP range requests in > django.views.static.serve? > > The primary benefit I see is that it makes files served up for and > "seek-able" with the django server. This generally isn't a problem > for small

Support byte range requests in django.views.static.serve

Is the Django community interested in supporting HTTP range requests in django.views.static.serve ? The primary benefit I see is that it makes files served up for and "seek-able" with the django server. This generally isn't a

Re: Should there be a "is" comperator: {% if A is B %}?

Hi all, For the use case brought up originally, note https://code.djangoproject.com/ticket/20684 In that spirit, I think the better solution for the more general case brought here is a filter, say tag_attr, which takes a name and a value and renders them appropriately: {% for name, value in a

Re: Should there be a "is" comperator: {% if A is B %}?

I think I'm +1. This seems to add some signal with zero noise. On Apr 11, 2014 4:35 AM, "Gregor Müllegger" wrote: > Casting to strings would make this example work. But will break in other > cases: > > dict((key, str(val)) for key, val in {'value': None}.items()) > => > > I don't want to say