From 1b4e9b5d5e6ee1199b998c49e322ca0c4e540ac6 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Fri, 23 Jan 2009 16:22:15 +0000 Subject: Path elements are always unicode during traversal now. --- docs/narr/traversal.rst | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) (limited to 'docs/narr/traversal.rst') diff --git a/docs/narr/traversal.rst b/docs/narr/traversal.rst index d77667355..9ff7329c5 100644 --- a/docs/narr/traversal.rst +++ b/docs/narr/traversal.rst @@ -285,14 +285,10 @@ context object implied by the current request. Unicode and Traversal --------------------- -By default, the traversal machinery by default attempts to decode each -path element in ``PATH_INFO`` from its natural byte string (``str`` -type) representation into Unicode using the UTF-8 encoding before -passing it to the ``__getitem__`` of a model object. If any path -segment in ``PATH_INFO`` is not decodeable using the UTF-8 decoding, a -TypeError is raised. - -The option named ``unicode_path_segments`` in -:ref:`environment_chapter` provides a mechanism that will disable this -behavior, causing traversal to pass path segments as plain byte string -objects to all model ``__getitem__`` methods. +The traversal machinery by default attempts to decode each path +element in ``PATH_INFO`` from its natural byte string (``str`` type) +representation into Unicode using the UTF-8 encoding before passing it +to the ``__getitem__`` of a model object. If any path segment in +``PATH_INFO`` is not decodeable using the UTF-8 decoding, a TypeError +is raised. + -- cgit v1.2.3