summaryrefslogtreecommitdiff
path: root/docs/narr/renderers.rst
AgeCommit message (Collapse)Author
2013-09-11appeaseChris McDonough
2013-09-08fix merge conflictChris McDonough
2013-09-05move templating bindings back into the templating chapterMichael Merickel
2013-09-05add index for custom template enginesMichael Merickel
2013-09-05remove the deprecated request.response_* attributesMichael Merickel
2013-09-05add a section mentioning external template bindingsMichael Merickel
2013-09-05more chameleon builtin referencesMichael Merickel
2013-09-04change focus from we to youMichael Merickel
2013-09-04remove some mako/chameleon renderer docsMichael Merickel
2013-07-18normalize notations used for string and json renderer return values, closes ↵Chris McDonough
#1005
2013-04-22Merge pull request #995 from tshepang/patch-2Tres Seaver
remove redundancy
2013-04-22Merge pull request #994 from tshepang/patch-1Tres Seaver
remove redundant text
2013-04-22Merge pull request #993 from tshepang/longTres Seaver
some doc improvements
2013-04-22remove redundancyTshepang Lekhonkhobe
2013-04-22remove redundant textTshepang Lekhonkhobe
Also, this fact has already been explained in the chapter, so mention that.
2013-04-22grammarTshepang Lekhonkhobe
2013-04-22simplify explanationTshepang Lekhonkhobe
The sentence was simply too long-winded (and not too clear).
2013-04-22no need to link to a chapter that follows immediatelyTshepang Lekhonkhobe
2013-04-01my.package.MyJinja2Renderer is registered for .jinja2 files not .jinjaCatalin Iacob
2013-04-01Fix wrong reference to non existent getAjax functionCatalin Iacob
2013-02-13add import in code blockMichael Merickel
2013-02-09avoid repetition; the heading already mentions that this stuff is deprecatedTshepang Lekhonkhobe
2013-01-23provide a link to the class; lineno for a 1-liner is overkillTshepang Lekhonkhobe
2013-01-23user 'deprecated' Sphinx directiveTshepang Lekhonkhobe
2013-01-23use 'versionadded' Sphinx directiveTshepang Lekhonkhobe
2013-01-23displaying line numbers for 1-line snippets is overkillTshepang Lekhonkhobe
2013-01-22consistency fixesTshepang Lekhonkhobe
2013-01-21fix typosTshepang Lekhonkhobe
2013-01-02eliminate other repeated wordsTshepang Lekhonkhobe
2013-01-01eliminate repeated "the" wordsTshepang Lekhonkhobe
2012-11-02typoCarlos de la Guardia
2012-08-29add newness markersChris McDonough
2012-05-03allow __json__ and custom adapters to accept request argChris McDonough
2012-04-18reverted back to using a component registry during json encodingMichael Merickel
2012-04-17default_encode->_default_encode, dumps->_dumps, massage docsChris McDonough
2012-04-16docs for json defaultsMichael Merickel
2012-03-29- Coverage and docs updates for custom JSON class.Chris McDonough
- Fork point: master now represents a future 1.4 release.
2012-03-28JSON-API rework and Object.__json__ supportWayne Witzel III
2012-03-28intermediate commitMichael Merickel
2012-02-22- New API: ``pyramid.config.Configurator.add_notfound_view``. This is aChris McDonough
wrapper for ``pyramid.Config.configurator.add_view`` which provides easy append_slash support. It should be preferred over calling ``add_view`` directly with ``context=HTTPNotFound`` as was previously recommended. - New API: ``pyramid.view.notfound_view_config``. This is a decorator constructor like ``pyramid.view.view_config`` that calls ``pyramid.config.Configurator.add_notfound_view`` when scanned. It should be preferred over using ``pyramid.view.view_config`` with ``context=HTTPNotFound`` as was previously recommended. - The older deprecated ``set_notfound_view`` Configurator method is now an alias for the new ``add_notfound_view`` Configurator method. This has the following impact: the ``context`` sent to views with a ``(context, request)`` call signature registered via the deprecated ``add_notfound_view``/``set_notfound_view`` will now be the HTTPNotFound exception object instead of the actual resource context found. Use ``request.context`` to get the actual resource context. It's also recommended to disuse ``set_notfound_view`` in favor of ``add_notfound_view``, despite the aliasing. - The API documentation for ``pyramid.view.append_slash_notfound_view`` and ``pyramid.view.AppendSlashNotFoundViewFactory`` was removed. These names still exist and are still importable, but they are no longer APIs. Use ``pyramid.config.Configurator.add_notfound_view(append_slash=True)`` or ``pyramid.view.notfound_view_config(append_slash=True)`` to get the same behavior. - The ``set_forbidden_view`` method of the Configurator was removed from the documentation. It has been deprecated since Pyramid 1.1. - The AppendSlashNotFoundViewFactory used request.path to match routes. This was wrong because request.path contains the script name, and this would cause it to fail in circumstances where the script name was not empty. It should have used request.path_info, and now does. - Updated the "Registering a Not Found View" section of the "Hooks" chapter, replacing explanations of registering a view using ``add_view`` or ``view_config`` with ones using ``add_notfound_view`` or ``notfound_view_config``. - Updated the "Redirecting to Slash-Appended Routes" section of the "URL Dispatch" chapter, replacing explanations of registering a view using ``add_view`` or ``view_config`` with ones using ``add_notfound_view`` or ``notfound_view_config``
2012-02-15Use req instead of r for #413. It's more likely that somebody is already ↵Chris McDonough
passing something named r, and a template may depend on its existence or nonexistence to conditionalize rendering a bit of html.
2012-02-15- The system value ``r`` is now supplied to renderers as an alias forChris McDonough
``request``. This means that you can now, for example, in a template, do ``r.route_url(...)`` instead of ``request.route_url(...)``. Fixes #413.
2012-02-15remove unused importsChris McDonough
2011-07-30Updated all of the docs to reflect the new pyramid.* settings prefix.Michael Merickel
2011-07-20- Reordered chapters in narrative section for better new user friendliness.Chris McDonough
- Added more indexing markers to sections in documentation.
2011-07-20add more index markersChris McDonough
2011-07-01Add JSONP rendererChris McDonough
2011-06-14merge httpexception-utils branchChris McDonough
2011-06-13- Remove IResponder abstraction in favor of more general IResponseChris McDonough
abstraction. - It is now possible to return an arbitrary object from a Pyramid view callable even if a renderer is not used, as long as a suitable adapter to ``pyramid.interfaces.IResponse`` is registered for the type of the returned object. See the section in the Hooks chapter of the documentation entitled "Changing How Pyramid Treats View Responses". - The Pyramid router now, by default, expects response objects returned from view callables to implement the ``pyramid.interfaces.IResponse`` interface. Unlike the Pyramid 1.0 version of this interface, objects which implement IResponse now must define a ``__call__`` method that accepts ``environ`` and ``start_response``, and which returns an ``app_iter`` iterable, among other things. Previously, it was possible to return any object which had the three WebOb ``app_iter``, ``headerlist``, and ``status`` attributes as a response, so this is a backwards incompatibility. It is possible to get backwards compatibility back by registering an adapter to IResponse from the type of object you're now returning from view callables. See the section in the Hooks chapter of the documentation entitled "Changing How Pyramid Treats View Responses". - The ``pyramid.interfaces.IResponse`` interface is now much more extensive. Previously it defined only ``app_iter``, ``status`` and ``headerlist``; now it is basically intended to directly mirror the ``webob.Response`` API, which has many methods and attributes. - Documentation changes to support above.
2011-06-11- Pyramid now expects Response objects to have a __call__Chris McDonough
method which implements the WSGI application interface instead of the three webob attrs status, headerlist and app_iter. Backwards compatibility exists for code which returns response objects that do not have a __call__. - pyramid.response.Response is no longer an exception (and therefore cannot be raised in order to generate a response). - Changed my mind about moving stuff from pyramid.httpexceptions to pyramid.response. The stuff I moved over has been moved back to pyramid.httpexceptions.