From a8e03b7efab6c8845fa8b21b4b8d8e628e8e77e5 Mon Sep 17 00:00:00 2001 From: michr Date: Wed, 14 Dec 2011 16:35:34 -0800 Subject: Signed contributor agreement --- CONTRIBUTORS.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CONTRIBUTORS.txt b/CONTRIBUTORS.txt index a449333cb..050225b5b 100644 --- a/CONTRIBUTORS.txt +++ b/CONTRIBUTORS.txt @@ -158,3 +158,5 @@ Contributors - Reed O'Brien, 2011/11/07 - Klee Dienes, 2011/10/30 + +- Michael Ryabushin, 2011/12/14 -- cgit v1.2.3 From 6747aa8072b645a302a218d36283045c2a8381c6 Mon Sep 17 00:00:00 2001 From: michr Date: Wed, 14 Dec 2011 16:46:00 -0800 Subject: Added in a warning in whats new 1.3 about wsgiref beign more strict about returning string headers where as paste.httpserver converted them implicitly. --- docs/whatsnew-1.3.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/whatsnew-1.3.rst b/docs/whatsnew-1.3.rst index 608db74cd..28c161ad0 100644 --- a/docs/whatsnew-1.3.rst +++ b/docs/whatsnew-1.3.rst @@ -101,6 +101,16 @@ actually recommended if you rely on proxying from Apache or Nginx to a ``pserve`` -invoked application. **The wsgiref server is not a production quality server.** See :ref:`alternate_wsgi_server` for more information. +.. warning:: + + Previously, paste.httpserver "helped" by converting header values that weren't + strings to strings. The wsgiref server, on the other hand implements the spec + more fully. This specifically may affect you if you are modifying headers on + your response. The following error might be an indicator of this problem: + **AssertionError: Header values must be strings, please check the type of + the header being returned.** A common case would be returning unicode headers + instead of string headers. + A new :mod:`pyramid.compat` module was added which provides Python 2/3 straddling support for Pyramid add-ons and development environments. -- cgit v1.2.3