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 HttpResponse.__init__. Essentially: to return a 406 status code when necessary, we have to wait until the HttpResponse is first used to see if we have a valid codec to encode with. This requires doing the check when the status_code is looked at, and also looking at the status_code in HttpResponse.__iter__ and HttpResponse._get_content. I've also been doing some testing with HttpResponseSendFile (#2131), and have made modifications to the regressiontests as well as to the functionality of the function itself. I tested it using guppy, and it appears that (with it using the FileWrapper class), it does not cause issues with the heap as mentioned in Trac. There is still a regression test that does not pass, but it is testing old behavior. I will work on that in the coming week. I also want to work on making sure that there is a robust way for users to change what sort of sendfile mechanism is associated with HttpResponseSendFile. At the moment it is just an environment setting that gets changed in mod_wsgi, and it uses "sendfile" in mod_python. I want to make it more customizable for people using custom handlers. See you next week! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
