summaryrefslogtreecommitdiff
path: root/docs/whatsnew-1.0.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/whatsnew-1.0.rst')
-rw-r--r--docs/whatsnew-1.0.rst27
1 files changed, 15 insertions, 12 deletions
diff --git a/docs/whatsnew-1.0.rst b/docs/whatsnew-1.0.rst
index 8602c5105..0ed6e21fc 100644
--- a/docs/whatsnew-1.0.rst
+++ b/docs/whatsnew-1.0.rst
@@ -1,4 +1,4 @@
-What's New In Pyramid 1.0
+What's New in Pyramid 1.0
=========================
This article explains the new features in Pyramid version 1.0 as compared to
@@ -62,8 +62,8 @@ fail if you do nothing to your existing :mod:`repoze.bfg` application.
However, you won't have to do much to use your existing BFG applications on
Pyramid. There's automation which will change most of your import statements
and ZCML declarations. See
-http://docs.pylonshq.com/pyramid/dev/tutorials/bfg/index.html for upgrade
-instructions.
+http://docs.pylonsproject.org/projects/pyramid/current/tutorials/bfg/index.html
+for upgrade instructions.
Pylons 1 users will need to do more work to use Pyramid, as Pyramid shares no
"DNA" with Pylons. It is hoped that over time documentation and upgrade code
@@ -92,15 +92,15 @@ BFG Conversion Script
The ``bfg2pyramid`` conversion script performs a mostly automated conversion
of an existing :mod:`repoze.bfg` application to Pyramid. The process is
-described in :ref:`converting_a_bfg_app`.
+described in "Converting a BFG Application to Pyramid".
Scaffold Improvements
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- The scaffolds now have much nicer CSS and graphics.
-- The ``development.ini``, generated by all scaffolds, is now configured
- to use the :term:`WebError` interactive exception debugger by default.
+- The ``development.ini``, generated by all scaffolds, is now configured to
+ use the WebError interactive exception debugger by default.
- All scaffolds have been normalized: each now uses the name ``main``
to represent the function that returns a WSGI application, and each now has
@@ -110,12 +110,15 @@ Scaffold Improvements
(``starter``, ``routesalchemy``, ``alchemy``, ``zodb``) instead of ZCML
configuration.
-- The ``pyramid_zodb``, ``pyramid_routesalchemy`` and ``pyramid_alchemy``
+- The ``pyramid_zodb``, ``routesalchemy`` and ``pyramid_alchemy``
scaffolds now use a default "commit veto" hook when configuring the
``repoze.tm2`` transaction manager in ``development.ini``. This prevents a
transaction from being committed when the response status code is within
- the 400 or 500 ranges. See also
- http://docs.repoze.org/tm2/#using-a-commit-veto.
+ the 400 or 500 ranges.
+
+ .. seealso::
+
+ See also http://docs.repoze.org/tm2/#using-a-commit-veto.
Terminology Changes
~~~~~~~~~~~~~~~~~~~
@@ -203,8 +206,8 @@ Mako
~~~~
In addition to Chameleon templating, Pyramid now also provides built-in
-support for :term:`Mako` templating. See :ref:`mako_templates` for more
-information.
+support for :term:`Mako` templating. See
+:ref:`available_template_system_bindings` for more information.
URL Dispatch
~~~~~~~~~~~~
@@ -249,7 +252,7 @@ ZCML Externalized
Pyramid core. Loading ZCML is now a feature of the :term:`pyramid_zcml`
package, which can be downloaded from PyPI. Documentation for the package
should be available via
- http://pylonsproject.org/projects/pyramid_zcml/dev/, which describes how to
+ http://docs.pylonsproject.org/projects/pyramid_zcml/en/latest/, which describes how to
add a configuration statement to your ``main`` block to reobtain this
method. You will also need to add an ``install_requires`` dependency upon
the ``pyramid_zcml`` distribution to your ``setup.py`` file.