| Age | Commit message (Collapse) | Author |
|---|
|
``__view_mapper__`` attribute. This setting can still be overridden by
configuration-specified ``view_mapper`` argument to ``add_view``.
|
|
``@view_config``.
|
|
add_view to view deriver
|
|
request time via a request attribute named ``override_renderer``, which
should be the name of a registered renderer. Useful to provide
"omnipresent" RPC for existing views.
- Convert ``add_view_mapper`` to ``set_view_mapper``. There will only be a
single default view mapper. We no longer register named utilities for view
mappers to provide alternates.
- Previoulsy the ``view_mapper`` argument was required to be the *name* of an
existing registered view mapper. We no longer register named utilities for
view mappers, so now if an extension wants to override the view mapper used
for a particular view registration, it can use the dotted name to a view
mapper class or provide that class as ``view_mapper``.
|
|
|
|
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.
|
|
This class can be used by third-party authentication policy developers to
help in the mechanics of authentication cookie-setting.
|
|
``unauthenticated_userid`` method. This method supports an important
optimization required by people who are using persistent storages which do
not support object caching and whom want to create a "user object" as a
request attribute.
- A new API has been added to the ``pyramid.security`` module named
``unauthenticated_userid``. This API function calls the
``unauthenticated_userid`` method of the effective security policy.
- An ``unauthenticated_userid`` method has been added to the dummy
authentication policy returned by
``pyramid.config.Configurator.testing_securitypolicy``. It returns the
same thing as that the dummy authentication policy's
``authenticated_userid`` method.
- Since the ``pyramid.interfaces.IAuthenticationPolicy`` interface now
specifies that a policy implementation must implement an
``unauthenticated_userid`` method, all third-party custom authentication
policies now must implement this method. It, however, will only be called
when the global function named ``pyramid.security.unauthenticated_userid``
is invoked, so if you're not invoking that, you will not notice any issues.
- The (non-API) method of all internal authentication policy implementations
previously named ``_get_userid`` is now named ``unauthenticated_userid``,
promoted to an API method. If you were overriding this method, you'll now
need to override it as ``unauthenticated_userid`` instead.
|
|
``__original_view__`` attribute which references the original view callable
(or class).
|
|
Conflicts:
pyramid/config.py
|
|
TemplateFile
|
|
|
|
|
|
|
|
Conflicts:
CONTRIBUTORS.txt
|
|
|
|
|
|
|
|
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).
|
|
|
|
preserve_view_attrs, make sure decorator preserves view attrs
|
|
|
|
|
|
Conflicts:
CHANGES.txt
pyramid/config.py
|
|
|
|
|
|
|
|
|
|
callables with a decorator at view registration time
|
|
|
|
resulting in exceptions when an exceptional root factory was encountered.
Instead of trying to resolve the view, if it cannot, it will now just print
``<unknown>``.
|
|
table. See the narrative documentation section within the "URL Dispatch"
chapter entitled "Displaying All Application Routes".
- Added narrative documentation section within the "URL Dispatch" chapter
entitled "Displaying All Application Routes" (for ``paster proutes``
command).
|
|
arguments to add_route work by raising an exception during configuration if
view-related arguments exist but no ``view`` argument is passed.
|
|
|
|
|
|
|
|
|
|
environment under IPython.
|
|
|
|
|
|
a new one replaces it.
|
|
is based on scanning.
- Changed the "ZODB + Traversal Wiki Tutorial" based on changes to
``pyramid_zodb`` Paster template.
|
|
"Preventing Cross-Site Request Forgery Attacks".
|
|
|
|
|
|
documentation chapter.
|
|
- Added "Finding a Resource With a Class or Interface in Lineage" to
Resources narrative chapter.
|
|
chapter.
- Added "Determining if a Resource is In The Lineage of Another Resource" to
Resources narrative chapter.
|
|
--------
- If a resource implements a ``__resource_url__`` method, it will be called
as the result of invoking the ``pyramid.url.resource_url`` function to
generate a URL, overriding the default logic. See the new "Generating The
URL Of A Resource" section within the Resources narrative chapter.
Documentation
-------------
- Added "Generating The URL Of A Resource" section to the Resources narrative
chapter (includes information about overriding URL generation using
``__resource_url__``).
- Added "Generating the Path To a Resource" section to the Resources
narrative chapter.
- Added "Finding a Resource by Path" section to the Resources narrative
chapter.
|
|
|
