On Oct 20, 2010, at 7:48 PM, and-py wrote:
> No browser or server has ever used or
> understood RFC2047 encoded-words in HTTP headers
"All generalizations are wrong" (Mark Twain, I think?)
I work on a codebase that includes a server and multiple client implementations
that support and actively
On Sat, 2010-10-09 at 18:11 -0400, P.J. Eby wrote:
> Ok; if you can submit patches...
Done: http://bugs.python.org/issue10155
> Note, by the way, that just because the environment is unicode on
> 3.x, doesn't mean it's WSGI-correct: WSGI requires that unicode
> environment strings be just byte
If i had a files inside the environ how i can encode the bytes when i going
to save them?
On Oct 9, 2010 6:11pm, "PJ Eby" wrote:
At 09:37 PM 10/9/2010 +0200, And Clover wrote:
On 10/06/2010 07:21 PM, PJ Eby wrote:
How would these relate to the Python 3.2 release? Can you make 3.x an
At 09:37 PM 10/9/2010 +0200, And Clover wrote:
On 10/06/2010 07:21 PM, P.J. Eby wrote:
How would these relate to the Python 3.2 release? Can you make 3.x and
2.x versions?
Yes, I have separate fixup code paths for 2.x and 3.x. 3.x faces the
reverse situation to that previously described, in
On 10/06/2010 07:21 PM, P.J. Eby wrote:
How would these relate to the Python 3.2 release? Can you make 3.x and
2.x versions?
Yes, I have separate fixup code paths for 2.x and 3.x. 3.x faces the
reverse situation to that previously described, in that os.environ is
accurate on Windows but need
At 01:28 PM 10/6/2010 +0200, And Clover wrote:
On 10/05/2010 04:23 AM, P.J. Eby wrote:
A preliminary update of the standalone (Python <3.x) version of wsgiref
is now available
Is there any interest in putting fixup code into wsgiref's
CGIHandler? I appreciate this is really ugly, but the CGI
On 10/05/2010 04:23 AM, P.J. Eby wrote:
A preliminary update of the standalone (Python <3.x) version of wsgiref
is now available
Is there any interest in putting fixup code into wsgiref's CGIHandler? I
appreciate this is really ugly, but the CGI-to-WSGI gateway is the most
logical place for
A preliminary update of the standalone (Python <3.x) version of
wsgiref is now available using "easy_install wsgiref==dev". Relevant
diffs are here:
http://svn.eby-sarna.com/?rev=2689&view=rev
This is preliminary work that'll need to be ported to the Python 3
version of wsgiref (note that
