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
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
This week was mostly administrative and very small changes. I finished
up 2131, 5241, 6527, 10190 pretty fully. Any further changes by the
end of GSoC should be pretty small. I have pushed a couple tickets
further back (particularly 9081 and related ideas), because they are
not strictly necessary
This week I tested HttpResponseSendFile with a boat load of server
configs. You can check out the compatible ones on my branch. It
(ticket #2131) looks to be pretty much complete on my branch. Let me
know what you think -- I have committed quite a few changes to docs
and the actual functional code
I incorporated a good patch from ticket #6527 that cleaned up
HttpResponse.__init__, which I have spent a lot of time looking at
lately. This wasn't any of my work, but from my experience with
HttpResponse, it looks like a good idea (and it makes the code more
pleasant to look at).
HttpResponse n
Greetings from Fort Collins, CO. I've been sampling from the New
Belgium Brewery here, and I am pretty upset that I will be missing it
on the east coast.
I've made significant updates to my "charset" improvements (spawned
from working on ticket #10190). This has required some changes to
HttpRespo
Not too much to report this week, except I have the HttpResponse
charset handling (ticket 10190) working and passing all the test
suites. I changed test_client_regress for this to work, because it was
expecting strange behavior. I have no doubt there is some tweaking to
be done to the code, and I
I continued work on charset/encoding related business in HttpResponse
(#10190). I committed the changes to my branch, if you want to check
them out. I am in the process of working on testing that the responses
are actually encoded properly, but the tests I have so far confirm
that at least the cor
If you take a look at my branch, you will see I have a feature in
progress that takes both the Accept-Charset header (provided that the
view passes along the request) and the Content-Type (which must be
provided in the view) into account.
http://code.djangoproject.com/browser/django/branches/soc2
Continued work on 10190. With Malcolm, I decided to see how it would
work to optionally pass along the HttpRequest to an HttpResponse. This
allows users to access various Accept-* headers, particularly in this
case Accept-Charset. Using this, I am working towards being compliant
with HTTP RFC 2616
If you read my GSoC Status update (http://groups.google.com/group/
django-developers/t/3b9147615e36e1a3 ), some of this is already in
there.
The main idea of ticket 10190 is to provide an option for users to
give a specific charset for an HttpResponse. The charset and encoding
should be the same
I spent a good amount of time working to synthesize the requirements
and work already done for ticket 2131 (which is to provide
HttpResponseSendFile with server-specific headers as well as a
fallback for servers without specific optimizations). I still have a
bit of confusion that I may enumerate
As scheduled, I got nothing visible done this week. My plan for the
coming week is to begin work on ticket #2131, as well as establish a
work flow with my Subversion branch and my local git revision control.
See you next week.
--~--~-~--~~~---~--~~
You received this
I have submitted a patch for ticket 10834,
http://code.djangoproject.com/ticket/10834
Nicolas and Malcolm both checked it out and approved it. That should
fulfill the requirement for the interim ticket.
For the project timeline/marching orders, here is what I know so far.
05/23 - 05/27 - I take
This will be the last of these lackluster updates for a while. My
finals are done on Monday, and everything associated with this school
year. I will get down to business hard as soon as I have ensured my
classes are in order.
Next week, Django, next week!
--~--~-~--~~~
Hello all,
It's been a busy week. I haven't gotten anything visible done. I've
got a lot of prep work and learning done (with my dev environment,
revision control, etc), but nothing spectacular. School ends next
week, so I am looking forward to getting moving on my interim ticket
once it does.
C
Happy Friday everyone. This week has been pretty busy with school,
again, but interspersed with some useful bits.
I selected ticket 10834 for my interim bug fix. It is closely linked
with my proposal description and should be a good way to start hashing
out a work flow for working on Django.
I h
Hello there django-dev, my name is Chris Cahoon. I'm a junior at the
University of Maryland, Baltimore County (UMBC), heading towards a BS
in CS. There's a good amount of auto-biography in my GSoC proposal, so
I'll leave that for later. I was accepted to GSoC with Malcolm
Tredinnick as my mentor,
18 matches
Mail list logo
