On 29 marras, 01:13, Wim Feijen wrote:
> Hi, the patch has been updated and now works.
>
> Still, feedback would be appreciated. So, Anssi, Jacob?
Apart of some whitespace errors the patch looks good to me.
There isn't last() method in the patch. Implementing one is going to
be a little more cha
Hi, the patch has been updated and now works.
Still, feedback would be appreciated. So, Anssi, Jacob?
- Wim
Op maandag 19 november 2012 22:48:36 UTC+1 schreef Wim Feijen het volgende:
>
> Hi,
>
> I do like the first() method and went ahead and *tried* to implement it.
>
> Ticket:
> https://code
>> - A hypothetical middleware that appends debug information to the end
>> of the response. debug-toolbar may be able to work like this.
> Looking for the boils down to the same problem as above, and can't be
> implemented without consuming the content for the same reason.
It can be done, it'
Hi Gavin,
The whole point of the HttpStreamingResponse API to access the content is to be
incompatible with HttpResponse. Otherwise it's too easy to consume streamed
content accidentally.
Re-introducing a common API ("streaming_content") would remove that benefit, it
would be confusing in the
On 27 marras, 21:11, Trey Raymond wrote:
> Hi folks,
> I'm a DB engineer working for Yahoo, and we have a new product using django
> that I'm onboarding. We see a variety of easily fixed issues, but one
> major one - there are 21 many-many tables here, yet they have auto
> increment primary keys.
- GzipMiddleware (compress_string(x) == compress_sequence([x]))
- StripWhitespaceMiddleware
- ContentDoctorMiddleware (https://github.com/unomena/django-content-doctor)
- A hypothetical middleware that appends debug information to the end
of the response. debug-toolbar may be able to work like
2012/11/28 Gavin Wahl
> I would like to avoid having two code paths, one with streaming and one
> without, in new middleware.
>
Hi Gavin,
Could you give an example of a middleware that:
- needs to alter the content,
- will work identically both on regular HttpResponses and
StreamingHttpResp
Hi folks,
I'm a DB engineer working for Yahoo, and we have a new product using django
that I'm onboarding. We see a variety of easily fixed issues, but one
major one - there are 21 many-many tables here, yet they have auto
increment primary keys. This of course is very slow on any platform, bu
We are experiencing the same problem that DavidR mentioned. We took the
patch
that was provided by #19048 and tested it out and it worked for us;
however, it
was closed as a duplicate of #8280.
They don't seem to be duplicates as #8280 is talking about the Django code
actually searching for .py
Hi Djangonauts,
I'm a frontend developer at a Django shop and lately we have doing a lot of
projects that customize the Django admin interface. Adding confirmation
popups, custom interface for certain types of content, etc. One very
frustrating part of this has been overriding or extending the
Our second milestone on the road to Django 1.5 came today, with the
release of the first beta package.
Blog post about it is here:
https://www.djangoproject.com/weblog/2012/nov/27/15-beta-1/
Release notes are here:
https://docs.djangoproject.com/en/dev/releases/1.5-beta-1/
And you can get the
I would like to avoid having two code paths, one with streaming and one
without, in new middleware.
If `HttpResponse` followed the the `streaming_content` API as well, when
writing a streaming-aware middleware instead of writing
if response.streaming:
response.streaming_content =
wr
It's for promotional purposes really - I want to add my employers,
PythonAnywhere, to the list of Django-Friendly-Web-Hosts
https://code.djangoproject.com/wiki/DjangoFriendlyWebHosts
But it's not entirely one-sided and evil-marketing-spammy. We do offer
Django hosting as part of our Free pla
I suggest that we merge the ORM Aggregation component to the Database
layer component.
The ORM Aggregation is the only subcomponent of the ORM. To be
consistet we should either have more ORM subcomponents or none at all.
I don't feel like splitting the Database layer into subcomponents
improves th
FTR, another solution is to intercept creation of tags with
DOMNodeInserted. Requires no monkey patch and is compatible with django &
django-grappelli out of the
box: https://github.com/yourlabs/django-autocomplete-light/commit/1f1e715e20
Thanks again for your answer (which I credited in the r
Wow, thanks a lot.
I would like to thanks everybody who answered. I have learned a lot from
this thread and thanks to you I believe I am a better programmer.
FTR, I've added an article to my blog which obsoletes the previous article.
Kind regards from Spain
On Tue, Nov 27, 2012 at 8:22 PM, Jav
16 matches
Mail list logo
