| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
and narrative docs.
- Break out awkward description of PasteDeploy entry points from
project chapter into its own Paste chapter.
|
|
|
|
than the ``repoze.zodbconn`` package to provide ZODB integration.
- The ZODB scaffold now uses the ``pyramid_zodbconn`` package rather than the
``repoze.zodbconn`` package to provide ZODB integration.
|
|
``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/).
|
|
|
|
|
|
|
|
|
|
|
|
use ``/projects/pyramid/current`` rather than ``/projects/pyramid/dev``.
|
|
|
|
http://stackoverflow.com/questions/6703850/cant-get-pyramid-to-work-with-mod-wsgi
|
|
inappropriately used ``DBSession.rollback()`` instead of
``transaction.abort()`` in one place.
- Wiki2 (SQLAlchemy + URL Dispatch) tutorial ``models.initialize_sql`` didn't
match the ``pyramid_routesalchemy`` scaffold function of the same name; it
didn't get synchronized when it was changed in the scaffold.
|
|
|
|
|
|
|
|
|
|
to depend on WebTest, and 2 tests failed as the result of changes to
Pyramid itself. These issues have been fixed.
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
Also add functional tests to the Wiki2 tutorial, similar to Wiki1.
|
|
|
|
|
|
|
|
|
|
pyramid.response
|
|
|
|
|
|
|
|
|
|
into ppaez-zodb-tutorial-test-reorg
|
|
|
|
- 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.
|
|
|
|
- New section in the main index
- Move Model and View tests there
- Added Functional tests
|
|
I was working through the wiki2 tutorial this morning and found some
slightly confusing bits. As I went along, I added the suggested changes
to my local files to make them match the tutorial's version, but found
several times that key parts were missing.
I'm not new to Python so this didn't slow me down, but thought some
clarifications might help new users.
|
|
|
|
|
|
- Sections sorted by general, views, templates
- List steps in the introduction
|
|
- Consolidate two sections and promote some to first level
- Add a couple of terms
|
|
|
|
|
