summaryrefslogtreecommitdiff
path: root/docs/tutorials/cmf
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2009-05-10 16:19:52 +0000
committerChris McDonough <chrism@agendaless.com>2009-05-10 16:19:52 +0000
commit6f318ae12bff899a8d29d725384a94c389039eb2 (patch)
tree9e727a298d0e89a3b11f084df1b384de2d5b041c /docs/tutorials/cmf
parent5cf1779a4df258740ec452c55b9f398a261aeb7b (diff)
downloadpyramid-6f318ae12bff899a8d29d725384a94c389039eb2.tar.gz
pyramid-6f318ae12bff899a8d29d725384a94c389039eb2.tar.bz2
pyramid-6f318ae12bff899a8d29d725384a94c389039eb2.zip
- In version 0.6.3, passing a ``get_root`` callback (a "root factory")
to ``repoze.bfg.router.make_app`` became optional if any ``route`` declaration was made in ZCML. The intent was to make it possible to disuse traversal entirely, instead relying entirely on URL dispatch (Routes) to resolve all contexts. However a compound set of bugs prevented usage of a Routes-based root view (a view which responds to "/"). One bug existed in `repoze.bfg.urldispatch``, another existed in Routes itself. To resolve this issue, the urldispatch module was fixed, and a fork of the Routes trunk was put into the "dev" index named ``Routes-1.11dev-chrism-home``. The source for the fork exists at `http://bitbucket.org/chrism/routes-home/ <http://bitbucket.org/chrism/routes-home/>`_; its contents have been reported to the upstream Routes developers and will hopefully be a part of the final Routes 1.11 release.
Diffstat (limited to 'docs/tutorials/cmf')
0 files changed, 0 insertions, 0 deletions