diff options
| author | Chris McDonough <chrism@agendaless.com> | 2010-07-30 01:30:19 +0000 |
|---|---|---|
| committer | Chris McDonough <chrism@agendaless.com> | 2010-07-30 01:30:19 +0000 |
| commit | d884698e3acf394d069a16930a679aa0c7298641 (patch) | |
| tree | 12bb338b3e1bb13e729b6afe6f4f7421b23daf92 /CHANGES.txt | |
| parent | 8acf88789221b0a726b9bb56936e4531a4b628a8 (diff) | |
| download | pyramid-d884698e3acf394d069a16930a679aa0c7298641.tar.gz pyramid-d884698e3acf394d069a16930a679aa0c7298641.tar.bz2 pyramid-d884698e3acf394d069a16930a679aa0c7298641.zip | |
Changes gardening.
Diffstat (limited to 'CHANGES.txt')
| -rw-r--r-- | CHANGES.txt | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt index 2daba6f4d..f029dca14 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -23,6 +23,24 @@ Bug Fixes wrong view matches when using URL dispatch and custom view predicates together. +- Pattern matches for a ``:segment`` marker in a URL dispatch route + pattern now always match at least one character. See "Backwards + Incompatibilities" below in this changelog. + +Backwards Incompatibilities +--------------------------- + +- A bug existed in the regular expression to do URL matching. As an + example, the URL matching machinery would cause the pattern + ``/{foo}`` to match the root URL ``/`` resulting in a match + dictionary of ``{'foo':u''}`` or the pattern ``/{fud}/edit might + match the URL ``//edit`` resulting in a match dictionary of + ``{'fud':u''}``. It was always the intent that ``:segment`` markers + in the pattern would need to match *at least one* character, and + never match the empty string. This, however, means that in certain + circumstances, a routing match which your application inadvertently + depended upon may no longer happen. + Documentation -------------- |