diff options
| author | Chris McDonough <chrism@agendaless.com> | 2009-02-05 08:27:08 +0000 |
|---|---|---|
| committer | Chris McDonough <chrism@agendaless.com> | 2009-02-05 08:27:08 +0000 |
| commit | dbab77392727456df89d3e91bd97899d919b6654 (patch) | |
| tree | 278c2b5de0154799b30f74e9eb14f6b537af3980 /docs/api | |
| parent | 00390896683d497cd8e6855727c3e6def3d20f82 (diff) | |
| download | pyramid-dbab77392727456df89d3e91bd97899d919b6654.tar.gz pyramid-dbab77392727456df89d3e91bd97899d919b6654.tar.bz2 pyramid-dbab77392727456df89d3e91bd97899d919b6654.zip | |
Backwards Incompatibilities
---------------------------
- The ``repoze.bfg.traversal.model_path`` API now returns a tuple
instead of a string. Previously it returned a string representing
the model path, with each segment name in the path joined together
via ``/`` characters, e.g. ``/foo/bar``. Now it returns a tuple,
where each segment is an element in the tuple e.g. ``('', 'foo',
'bar')`` (the leading empty element indicates that this path is
absolute). This change was (as discussed on the repoze-dev
maillist) necessary to accomodate model objects which themselves
have names that contain the ``/`` character. See the API
documentation for ``repoze.bfg.traversal.model_path`` for more
information.
- The ``repoze.bfg.traversal.find_model`` API no longer implicitly
converts unicode path representations into a UTF-8 string. Callers
should either use path tuples or use the guidelines about passing a
string ``path`` argument described in its API documentation.
Features
--------
- The ``find_model`` API now accepts "path tuples" (see the above note
regarding ``model_path``) as well as string path representations as
a ``path`` argument.
Diffstat (limited to 'docs/api')
0 files changed, 0 insertions, 0 deletions
