RedHatTraining/pyramid.git

			@@ -53,6 +53,9 @@

			- Slightly improved interface docs for ``IAuthorizationPolicy``.

			- Minimally explain usage of custom regular expressions in URL dispatch
			replacement markers within URL Dispatch chapter.

			Deprecations
			-------------

			@@ -252,6 +252,18 @@
			because there is a literal part of ``.`` (period) between the two replacement
			markers ``{name}`` and ``{ext}``.

			Replacement markers can optionally specify a regular expression which will be
			used to decide whether a path segment should match the marker. To specify
			that a replacement marker should match only a specific set of characters as
			defined by a regular expression, you must use a slightly extended form of
			replacement marker syntax. Within braces, the replacement marker name must
			be followed by a colon, then directly thereafter, the regular expression.
			For example, under the hood, the replacement marker ``{foo}`` can more
			verbosely be spelled as ``{foo:[^/]+}``. The default regular expression
			associated with a replacement marker ``[^/]+`` matches one or more characters
			which are not a slash. You can use an arbitrary regular expression here to
			match a sequence of characters.

			It is possible to use two replacement markers without any literal characters
			between them, for instance ``/{foo}{bar}``. However, this would be a
			nonsensical pattern without specifying a custom regular expression to

			@@ -1,12 +1,6 @@
			Pyramid TODOs
			=============

			Must-Have (before 1.0)
			----------------------

			- Explain ``{foo:<regex>}`` pattern formatting and purpose better in
			within URL dispatch chapter.

			Should-Have
			-----------