I just released repoze.bfg 1.0a3 to the BFG "current" index 
(http://dist.repoze.org/bfg/current/simple).  This release removed a dependency 
on Routes and fixed bugs related to running BFG on GAE.

The documentation at http://docs.repoze.org/bfg has also been updated.

1.0a3 (2009-06-24)

Implementation Changes

- ``repoze.bfg`` no longer relies on the Routes package to interpret
   URL paths.  All known existing ``path`` patterns will continue to
   work with the reimplemented logic, which lives in
   ``repoze.bfg.urldispatch``.  ``<route>`` ZCML directives which use
   certain attributes (uncommon ones) may not work (see "Backwards
   Incompatibilities" below).

Bug Fixes

- ``model_url`` when passed a request that was generated as a result
   of a route match would fail in a call to ``route.generate``.

- BFG-on-GAE didn't work due to a corner case bug in the fallback
   Python implementation of ``threading.local`` (symptom:
   "Initialization arguments are not supported").  Thanks to Michael
   Bernstein for the bug report.


- Added a "corner case" explanation to the "Hybrid Apps" chapter
   explaining what to do when "the wrong" view is matched.

- Use ``repoze.bfg.url.route_url`` API in tutorials rather than Routes
   ``url_for`` API.


- Added the ``repoze.bfg.url.route_url`` API.  This API allows you to
   generate URLs based on ``<route>`` declarations.  See the URL
   Dispatch narrative chapter and the "repoze.bfg.url" module API
   documentation for more information.

Backwards Incompatibilities

- As a result of disusing Routes, using the Routes ``url_for`` API
   inside a BFG application (as was suggested by previous iterations of
   tutorials) will no longer work.  Use the
   ``repoze.bfg.url.route_url`` method instead.

- The following attributes on the ``<route>`` ZCML directive no longer
   work: ``encoding``, ``static``, ``filter``, ``condition_method``,
   ``condition_subdomain``, ``condition_function``, ``explicit``, or
   ``subdomains``.  These were all Routes features.

- The ``<route>`` ZCML directive no longer supports the
   ``<requirement>`` subdirective.  This was a Routes feature.

Repoze-dev mailing list

Reply via email to