summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2010-07-02 01:47:47 +0000
committerChris McDonough <chrism@agendaless.com>2010-07-02 01:47:47 +0000
commitb29429e470c093573f3735b0dbf09d42c29cfe4d (patch)
tree8dfa266de6bd0f10a80d9654fe3ddf3a7897c467 /CHANGES.txt
parent78a659d76e5bbb7544212174f010c1f50f8bcbe6 (diff)
downloadpyramid-b29429e470c093573f3735b0dbf09d42c29cfe4d.tar.gz
pyramid-b29429e470c093573f3735b0dbf09d42c29cfe4d.tar.bz2
pyramid-b29429e470c093573f3735b0dbf09d42c29cfe4d.zip
- The ``repoze.bfg.url.route_url`` API has changed. If a keyword
``_app_url`` is present in the arguments passed to ``route_url``, this value will be used as the protocol/hostname/port/leading path prefix of the generated URL. For example, using an ``_app_url`` of ``http://example.com:8080/foo`` would cause the URL ``http://example.com:8080/foo/fleeb/flub`` to be returned from this function if the expansion of the route pattern associated with the ``route_name`` expanded to ``/fleeb/flub``. - It is now possible to use a URL as the ``name`` argument fed to ``repoze.bfg.configuration.Configurator.add_static_view``. When the name argument is a URL, the ``repoze.bfg.url.static_url`` API will generate join this URL (as a prefix) to a path including the static file name. This makes it more possible to put static media on a separate webserver for production, while keeping static media package-internal and served by the development webserver during development.
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt27
1 files changed, 27 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index d56f51e4e..28322d42f 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -48,6 +48,23 @@ Features
add_route('ym', '/:year/:month', custom_predicates=(twenty_ten,))
add_route('ymd', '/:year/:month:/day', custom_predicates=(twenty_ten,))
+- The ``repoze.bfg.url.route_url`` API has changed. If a keyword
+ ``_app_url`` is present in the arguments passed to ``route_url``,
+ this value will be used as the protocol/hostname/port/leading path
+ prefix of the generated URL. For example, using an ``_app_url`` of
+ ``http://example.com:8080/foo`` would cause the URL
+ ``http://example.com:8080/foo/fleeb/flub`` to be returned from this
+ function if the expansion of the route pattern associated with the
+ ``route_name`` expanded to ``/fleeb/flub``.
+
+- It is now possible to use a URL as the ``name`` argument fed to
+ ``repoze.bfg.configuration.Configurator.add_static_view``. When the
+ name argument is a URL, the ``repoze.bfg.url.static_url`` API will
+ generate join this URL (as a prefix) to a path including the static
+ file name. This makes it more possible to put static media on a
+ separate webserver for production, while keeping static media
+ package-internal and served by the development webserver during
+ development.
Documentation
-------------
@@ -68,6 +85,16 @@ Documentation
- A section named ``Custom Route Predicates`` was added to the URL
Dispatch narrative chapter.
+- The Static Resources chapter has been updated to mention using
+ ``static_url`` to generate URLs to external webservers.
+
+Internal
+--------
+
+- Removed ``repoze.bfg.static.StaticURLFactory`` in favor of a new
+ abstraction revolving around the (still-internal)
+ ``repoze.bfg.static.StaticURLInfo`` helper class.
+
1.3a3 (2010-05-01)
==================