| Age | Commit message (Collapse) | Author |
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
a named implementation of a ``pyramid.interfaces.IViewMapperFactory``
interface. Its name can be passed as a ``view_mapper`` argument to
``config.add_view``. A view mapper allows objects that are meant to be
used as view callables to have an arbitrary argument list and an arbitrary
result. This feature will be used by Pyramid extension developers, not by
"civilians".
- New constructor argument to Configurator: ``default_view_mapper``. Useful
to create systems that have view callables with alternate default calling
conventions.
- ``view_mapper`` argument to ``add_view`` should now be a view mapper *name*
rather than an implementation.
- Add ``view_mapper`` argument to ``view_config`` decorator constructor.
- Remove (non-API) function of config.py named _map_view.
- Fix docstring for ``decorator`` argument to add_view.
- Factor invocation of view mapper into a viewderiver method.
- Promote view rendering and decorating into viewderiver, out of view mapper.
- Make requestonly into a function rather than a method of the default view
mapper.
|
|
than a large number of standalone functions (a side effect of the
``view_mapper`` refactoring).
- The ``pyramid.renderer.RendererHelper`` class has grown a ``render_view``
method, which is used by the default view mapper (a side effect of the
``view_mapper`` refactoring).
- The object passed as ``renderer`` to the "view deriver" is now an instance
of ``pyramid.renderers.RendererHelper`` rather than a dictionary (a side
effect of ``view_mapper`` refactoring).
|
|
|
|
"advanced configuration" chapter.
|
|
|
|
a prefix unless it's a URL, added an example of a root-relative static view
fallback for URL dispatch, added an example of creating a simple view that
returns the body of a file.
|
|
|
|
deal with configuration conflicts, two-phase configuration, ``include`` and
``commit``.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
"Preventing Cross-Site Request Forgery Attacks".
|
|
|
|
|
|
documentation chapter.
|
|
documentation.
|
|
|