Re: Patch[1] for http_response.py for quixote-2.1

> > How does that matter if the user (quixote developer) changes
> > HTTPResponse.DEFAULT_CHARSET to something else (expecting that
> > change to be reflected everywhere)?
> 
> Changing DEFAULT_CHARSET has no effect on what is the default for
> the HTTP protocol.  If you don't provide a second argument to
> set_content_type then it's as if you did not provide the 'charset'
> parameter on the Content-Type header.

I needed some time to understand what you are saying here... 

I beleive you are thinking from the standpoint of the HTTP standard (*),
but what I'm thinking is from the standpoint of a quixote user (the
application developer).

If I have setup the DEFAULT_CHARSET property, I'd expect this to apply
for everything. Now, if I use set_content_type to set the 'Contet-type',
I might not know that it also expects a charset parameter, 
and surelly I'd not expect that it will set the charset to 'iso-8859-1'
if I don't specify any. I'd expect it to inherit the defaults I've setup
before.

[*]
BTW the iso-8859-1 being the default charset in HTTP is widelly
considered the worst choice in the HTTP standard.


-- 
damjan | дамјан
This is my jabber ID --> [email protected] <-- not my mail address!!!