summaryrefslogtreecommitdiff
path: root/docs/narr
AgeCommit message (Collapse)Author
2011-05-14add 'What's new In Pyramid 1.1' documentChris McDonough
2011-05-14use lingua in docs (thanks to wichert)Chris McDonough
2011-05-13- The ``add_route`` method of the Configurator now accepts a ``static``Chris McDonough
argument. If this argument is ``True``, the added route will never be considered for matching when a request is handled. Instead, it will only be useful for URL generation via ``route_url`` and ``route_path``. See the section entitled "Static Routes" in the URL Dispatch narrative chapter for more information.
2011-05-13- Added documentation for a "multidict" (e.g. the API of ``request.POST``) asChris McDonough
interface API documentation.
2011-05-04code refactoring for showing route->view relationship more correctly; tests ↵cguardia
and docs for pull request
2011-04-25spell it out entirelyChris McDonough
2011-04-24Merge branch 'master' of https://github.com/jdnavarro/pyramid into ↵Chris McDonough
jdnavarro-master
2011-04-24fix rendering issueChris McDonough
2011-04-23BFG -> PyramidDanny Navarro
2011-04-22- Make sure deprecation warnings aren't raised when tests are run.Chris McDonough
- Modify documentation for cross-referencing. - Use add_view(viewname) syntax rather than add_view(view=viewname) syntax for normalization. - Use warnings.warn rather than zope.deprecated in order to make testing easier. - Move tests which test deprecated methods of configurator to a separate test case.
2011-04-22Merge branch 'disambiguate_add_route' of ↵Chris McDonough
https://github.com/mmerickel/pyramid into mmerickel-disambiguate_add_route
2011-04-21add 'adding a custom settings'Chris McDonough
2011-04-20Converting docs to deprecate view parameters in config.add_route.Michael Merickel
2011-04-18- Deprecated all assignments to ``request.response_*`` attributes such asChris McDonough
``request.response_content_type = 'foo'``. Assignments and mutations of the following request attributes that were considered by the framework for response influence are now deprecated: ``response_content_type``, ``response_headerlist``, ``response_status``, ``response_charset``, and ``response_cache_for``. Instead of assigning these to the request object for detection by the rendering machinery, users should use the appropriate API of the Response object created by accessing ``request.response`` (e.g. ``request.response_content_type = 'abc'`` -> ``request.response.content_type = 'abc'``). - Custom request objects are now required to have a ``response`` attribute (or reified property) if they are meant to be used with renderers. This ``response`` attribute should be an instance of the class ``pyramid.response.Response``. - The JSON and string renderer factories now use ``request.response.content_type`` rather than ``request.response_content_type``. They determine whether they should set the content type of the response by comparing the response's content type against the default (usually ``text/html``); if the content type is not the default, the renderer changes the content type (to ``application/json`` or ``text/plain`` for JSON and string renderers respectively). - Made it possible to assign to and delete ``pyramid.testing.DummyRequest.registry`` (bugfix).
2011-04-13- Add missing docs reference toChris McDonough
``pyramid.config.Configurator.set_view_mapper`` and refer to it within Hooks chapter section named "Using a View Mapper".
2011-04-11pyramid_sqla -> akhetChris McDonough
2011-04-11add description of MANIFEST.inChris McDonough
2011-04-11make prettierChris McDonough
2011-03-29fixed typocguardia
2011-03-25Moved the content that was put into whatsnew-1.0.rst into the CHANGES.txtJoe Dallago
file, b/c the terminology change doesn't apply to version 1.0. Also changed the output of the paster create command in project.rst back to its original state.
2011-03-24It was decided that pyramid would undergo a terminology change.Joe Dallago
'Paster templates' will now be refered to as 'scaffolds,' while 'rendered templates' will remain as 'templates.' I have changed the docs to reflect this change in terminology.
2011-03-24Merge remote branch 'source/master'Alexandre Bourget
Conflicts: docs/narr/hooks.rst
2011-03-24Fix some typos.Alexandre Bourget
2011-03-02Closes #125Chris McDonough
2011-02-28Fix authentication policy example.Chris McDonough
Closes #137
2011-02-26it's request_paramChris McDonough
2011-02-25typoChris McDonough
2011-02-13Merge branch 'master' of https://github.com/lambacck/pyramid into ↵Chris McDonough
lambacck-master
2011-02-12Add make_localizer function & docs & testsChristopher Lambacher
2011-02-12fix typoChris McDonough
2011-02-05fix conflictsChris McDonough
2011-02-02Wrong name for variableChris Beelby
2011-02-02Capitalization fixChris Beelby
2011-01-30fix referencesChris McDonough
2011-01-30More errors in narrative fixed.Chris Beelby
2011-01-30fix too-long linesChris McDonough
2011-01-30too-long lineChris McDonough
2011-01-30- Remove duplication of ``add_route`` API documentation from URL DispatchChris McDonough
narrative chapter.
2011-01-30inappropriate mentions of alternate declarative formsChris McDonough
2011-01-30remove reference to ZCML directives; doesnt work in printed bookChris McDonough
2011-01-30remove direct reference to pyramid_cookbook; doesnt work in printed versionChris McDonough
2011-01-30remove reference to static ZCML directive; cant refer to it from printed bookChris McDonough
2011-01-29- Changed "Cleaning up After a Request" section in the URL Dispatch chapterChris McDonough
to use ``request.add_finished_callback`` instead of jamming an object with a ``__del__`` into the WSGI environment.
2011-01-29Merge branch 'master' of https://github.com/osmaker/pyramid into osmaker-masterChris McDonough
2011-01-29no longer brokenChris McDonough
2011-01-29renderingsChris McDonough
2011-01-28shorten too-long lines for latexChris McDonough
2011-01-28render URL properlyChris McDonough
2011-01-28minor grammar fixes ('a' vs 'an')Kyle Johnson
2011-01-28Removed reference to Zope XML namespace since this is a Mako example. Also ↵Chris Beelby
Mako in general does not require such well-formed documents and it is perhaps more accurate of a typical mako template to make the example very basic.