From 74db82d177093f4b1102d70832f8abd9b894dd61 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Thu, 22 Jan 2009 08:59:51 +0000 Subject: - The ``unicode_path_segments`` configuration variable and the ``BFG_UNICODE_PATH_SEGMENTS`` configuration variable have been removed. Path segments are now always passed to model ``__getitem__`` methods as unicode. "True" has been the default for this setting since 0.5.4, but changing this configuration setting to false allowed you to go back to passing raw path element strings to model ``__getitem__`` methods. This services a speed goal (we get about +80 req/s by removing the check), and it's clearer just to always expect unicode path segments in model ``__getitem__`` methods. --- docs/narr/environment.rst | 10 ---------- 1 file changed, 10 deletions(-) (limited to 'docs') diff --git a/docs/narr/environment.rst b/docs/narr/environment.rst index 69dc98e25..6df4157e2 100644 --- a/docs/narr/environment.rst +++ b/docs/narr/environment.rst @@ -39,16 +39,6 @@ application-specific configuration settings. +---------------------------------+-----------------------------+----------------------------------------+ | ``BFG_DEBUG_ALL`` | ``debug_all`` | Turns all debug_* settings on. | +---------------------------------+-----------------------------+----------------------------------------+ -| ``BFG_UNICODE_PATH_SEGMENTS`` | ``unicode_path_segments`` | Defaults to ``true``. When ``true``, | -| | | URL path segment names will be passed | -| | | to model object ``__getitem__`` | -| | | methods by the BFG model graph | -| | | traverser as ``unicode`` types rather | -| | | than as ``str`` types; path segments | -| | | will be assumed to be UTF-8 encoded. | -| | | When ``false``, pass path segments | -| | | as undecoded ``str`` types. | -+---------------------------------+-----------------------------+----------------------------------------+ Examples -------- -- cgit v1.2.3