…tead of allowing them to find their way into resolveConflicts).
…erver runners from the 1.3 branch. This change is to primarily allow scaffolding authors to rely on the wsgiref entry point for projects that are meant to work on both Pyramid 1.2.5 and 1.3.X.
…ation`` >= 3.8.0.
…mplates Rationale: Mako template renderers can be specified using an absolute asset spec. An entire application can be written with such asset specs, requiring no ordered lookup path.
…enerates a new CSRF token if one doesn't yet exist.
…tring comparator. See #320 for more info. References issue#320.
no-longer "double-decoded" during traversal and when encountered in a route subpath (or other star-arg pattern). As a result, a new API named ``pyramid.traversal.traversal_path_info`` was added to the system. This function accepts an already-URL-decoded string and returns a tuple of Unicode objects. This API is used internally by Pyramid in all places that ``pyramid.traversal.traversal_path`` used to be used. The ``traversal_path`` function remains for backwards compatibility, however, and can still be used when a path is encoded. See #349 for more information. Closes #349.
This is required when reissueing cookies which include a token: WebOb returns the tokens from a cookie as unicode instances, so remember() must be able to deal with them when refreshing. This is a backport of dd5a91e to the 1.2 branch.
testing dependency. - Pyramid now depends on a ``zope.interface`` version greater than or equal to 3.8.0.
…added in an "include". See #266 .
…ents from UTF-8 to Unicode before checking whether a segment matches literally one of ``.``, the empty string, or ``..`` in case there's some sneaky way someone might tunnel those strings via UTF-8 that don't match the literals before decoded.