…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.
…f it's missing
…tring comparator. See #320 for more info. References issue#320.
This factors out the timing-invariant string comparison code from session.py and re-uses it for signature checking in AuthTkt code.
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.