| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
Advanced Configuration narrative chapter.
|
|
(a backwards compatibility shim) now issues a deprecation warning.
|
|
|
|
|
|
paster templates 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.
|
|
|
|
narrative chapter.
|
|
|
|
|
|
|
|
|
|
now ``403 Forbidden``. It was previously ``401 Unauthorized``, for
backwards compatibility purposes with ``repoze.bfg``. This change will
cause problems for users of Pyramid with ``repoze.who``, which intercepts
``401 Unauthorized`` by default, but allows ``403 Forbidden`` to pass
through. Those deployments will need to configure ``repoze.who`` to also
react to ``403 Forbidden``.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
added: ``pyramid.traversal.find_model``, ``pyramid.traversal.model_path``,
``pyramid.traversal.model_path_tuple``, ``pyramid.url.model_url``. The
instructions emitted by the deprecation warnings instruct the developer to
change these method spellings to their ``resource`` equivalents. This is a
consequence of the mass concept rename of "model" to "resource" performed
in 1.0a7.
|
|
|
|
"Renderers" chapter in a section named "Overriding A Renderer at Runtime".
|
|
--------
- ``pyramid.testing.setUp`` and ``pyramid.testing.tearDown`` have been
undeprecated. They are now the canonical setup and teardown APIs for test
configuration, replacing "direct" creation of a Configurator. This is a
change designed to provide a facade that will protect against any future
Configurator deprecations.
Paster Templates
----------------
- All paster templates now use ``pyramid.testing.setUp`` and
``pyramid.testing.tearDown`` rather than creating a Configurator "by hand"
within their ``tests.py`` module, as per decision in features above.
Documentation
-------------
- The wiki and wiki2 tutorials now use ``pyramid.testing.setUp`` and
``pyramid.testing.tearDown`` rather than creating a Configurator "by hand",
as per decision in features above.
- The "Testing" narrative chapter now explains ``pyramid.testing.setUp`` and
``pyramid.testing.tearDown`` instead of Configurator creation and
``Configurator.begin()`` and ``Configurator.end()``.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
implementation should return a *new* token if one doesn't already exist in
the session (previously it would return None). The internal sessioning
implementation has been changed.
|
|
|
|
- Document ``__view_mapper__`` attribute and ``mapper`` argument to view
configuration for view callable view mapper preference.
|
|
- Document ``decorator`` and ``mapper`` arguments in various places.
|
|
|
|
|
|
|
|
on the "current" route (if any) and its matchdict values.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|