From 49425bcce4f754d706bb7917f24c7e1b36231d3c Mon Sep 17 00:00:00 2001 From: Bruno Binet Date: Thu, 13 Oct 2011 02:24:39 +0300 Subject: fix static_url docstring about absolute path since pyramid 1.2, the path can be absolute and no ValueError is raised anymore (see commit b8c79771a186f1032635fc640b3cecc2c9e281ad ) --- pyramid/url.py | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/pyramid/url.py b/pyramid/url.py index 7a7dd3b4c..2402a79c4 100644 --- a/pyramid/url.py +++ b/pyramid/url.py @@ -340,10 +340,9 @@ class URLMethodsMixin(object): The ``path`` argument points at a file or directory on disk which a URL should be generated for. The ``path`` may be either a - relative path (e.g. ``static/foo.css``) or a :term:`asset - specification` (e.g. ``mypackage:static/foo.css``). A ``path`` - may not be an absolute filesystem path (a :exc:`ValueError` will - be raised if this function is supplied with an absolute path). + relative path (e.g. ``static/foo.css``) or an absolute path (e.g. + ``/abspath/to/static/foo.css``) or a :term:`asset specification` + (e.g. ``mypackage:static/foo.css``). The purpose of the ``**kw`` argument is the same as the purpose of the :meth:`pyramid.request.Request.route_url` ``**kw`` argument. See -- cgit v1.2.3