| Age | Commit message (Collapse) | Author |
|
|
|
|
|
- minor grammar and reST fixes
|
|
|
|
|
|
|
|
- fix css in zodb scaffold and wiki tutorial previous steps
|
|
- add intersphinx targets to wiki/*
|
|
- update templates and static assets for new design
|
|
- sort imports to be consistent with scaffold setup.py
- update templates, static assets
|
|
|
|
|
|
|
|
* This avoids having to update the link multiple times.
* Also, mention their location, in case user has Pyramid checkout.
|
|
|
|
|
|
|
|
- Moved the selection of the templates to
the Design chapter
- Improved the Views section in the Design chapter
- Normalize in both tutorials
|
|
- As suggested by Paulo in the PyCon sprint
|
|
|
|
- Sections 'Viewing the Application in a Browser' in the
'Defining the Domain Model' and 'Defining the Views'
chapters now offer a quick link in both wiki tutorials,
as suggested by Paulo.
|
|
from ``scan``).
|
|
|
|
|
|
added a hide toc for glossary to prevent warnings
|
|
``resource_url``, ``static_url``, and ``current_route_url`` methods of the
request rather than the function variants imported from ``pyramid.url``.
|
|
package at all; configuration in the ``production.ini`` file which used to
require its ``error_catcher`` middleware has been removed. Configuring
error catching / email sending is now the domain of the ``pyramid_exclog``
package (see https://docs.pylonsproject.org/projects/pyramid_exclog/dev/).
|
|
|
|
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.
|
|
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.
|
|
|
|
pyramid.response
|
|
- New section in the main index
- Move Model and View tests there
- Added Functional tests
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
book with older sphinx)
|
|
any overly long lines in the PDF rendering.
Changes to .rst files:
(docs/tutorials/wiki/authorization.rst)
(docs/tutorials/wiki/definingviews.rst)
(docs/tutorials/wiki2/authorization.rst)
(docs/tutorials/wiki2/definingviews.rst)
1. For included templates, added :tab-width: 2 options.
2. wiki2/authorization.rst: Wrong markup for file names __init__.py and
views.py just after the subhead "Adding security.py".
Changes to .py files: Folded a few long lines.
(docs/tutorials/wiki/src/basiclayout/tutorial/views.py)
(docs/tutorials/wiki/src/authorization/tutorial/views.py)
(docs/tutorials/wiki/src/views/tutorial/views.py)
(docs/tutorials/wiki2/src/basiclayout/tutorial/models.py)
(docs/tutorials/wiki2/src/models/tutorial/models.py)
Changes to .pt files: Broke long lines; reformatted for 2-space
indentation using tabs.
(docs/tutorials/wiki/src/authorization/tutorial/templates/edit.pt)
(docs/tutorials/wiki/src/authorization/tutorial/templates/login.pt)
(docs/tutorials/wiki/src/authorization/tutorial/templates/view.pt)
(docs/tutorials/wiki/src/views/tutorial/templates/edit.pt)
(docs/tutorials/wiki/src/views/tutorial/templates/view.pt)
(docs/tutorials/wiki2/src/authorization/tutorial/templates/edit.pt)
(docs/tutorials/wiki2/src/authorization/tutorial/templates/login.pt)
(docs/tutorials/wiki2/src/authorization/tutorial/templates/view.pt)
(docs/tutorials/wiki2/src/views/tutorial/templates/edit.pt)
(docs/tutorials/wiki2/src/views/tutorial/templates/view.pt)
|
|
|
|
|
|
|
|
|
|
is based on scanning.
- Changed the "ZODB + Traversal Wiki Tutorial" based on changes to
``pyramid_zodb`` Paster template.
|
|
|
|
instruct you to run a test which would fail because the view callable
generated by the ``pyramid_zodb`` tutorial used a one-arg view callable,
but the test in the sample code used a two-arg call.
- Updated ZODB+Traversal tutorial setup.py of all steps to match what's
generated by ``pyramid_zodb``.
|
|
to :app:`Pyramid`. A custom role setting was added to ``docs/conf.py`` to
allow for this. (internal)
|