Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Jul 22, 2011
  1. Chris McDonough

    - Change all scaffolding templates that point to docs.pylonsproject.o…

    mcdonc authored
    …rg to
    
      use ``/projects/pyramid/current`` rather than ``/projects/pyramid/dev``.
Commits on Jul 17, 2011
  1. Chris McDonough

    garden

    mcdonc authored
  2. Chris McDonough

    garden

    mcdonc authored
  3. Chris McDonough

    garden

    mcdonc authored
Commits on Jul 13, 2011
  1. Chris McDonough

    - We now clear ``request.response`` before we invoke an exception vie…

    mcdonc authored
    …w; an
    
      exception view will be working with a request.response that has not been
      touched by any code prior to the exception.
  2. Chris McDonough

    garden

    mcdonc authored
  3. Chris McDonough

    garden

    mcdonc authored
Commits on Jul 12, 2011
  1. Chris McDonough

    - The ``pyramid_routesalchemy`` and ``pyramid_alchemy`` scaffolds

    mcdonc authored
      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.
  2. Chris McDonough

    garden

    mcdonc authored
  3. Chris McDonough

    - The ``Configurator.add_route`` method allowed two routes with the same

    mcdonc authored
      route to be added without an intermediate ``config.commit()``.  If you now
      receive a ``ConfigurationError`` at startup time that appears to be
      ``add_route`` related, you'll need to either a) ensure that all of your
      route names are unique or b) call ``config.commit()`` before adding a
      second route with the name of a previously added name or c) use a
      Configurator that works in ``autocommit`` mode.
  4. Chris McDonough
  5. Chris McDonough

    reviewed

    mcdonc authored
Commits on Jul 10, 2011
  1. Chris McDonough

    garden

    mcdonc authored
Commits on Jul 6, 2011
  1. Chris McDonough

    garden

    mcdonc authored
  2. Chris McDonough

    garden

    mcdonc authored
  3. Chris McDonough

    garden

    mcdonc authored
Commits on Jul 4, 2011
  1. Chris McDonough

    garden

    mcdonc authored
Commits on Jul 1, 2011
  1. Chris McDonough

    garden

    mcdonc authored
Commits on Jun 30, 2011
  1. Chris McDonough

    garden

    mcdonc authored
  2. Chris McDonough

    garden

    mcdonc authored
Commits on Jun 26, 2011
  1. Chris McDonough

    - Accessing or setting deprecated response_* attrs on request

    mcdonc authored
      (e.g. ``response_content_type``) now issues a deprecation warning at access
      time rather than at rendering time.
Commits on Jun 22, 2011
  1. Chris McDonough

    garden

    mcdonc authored
Commits on Jun 20, 2011
  1. Chris McDonough

    - Register the default exception view for context of

    mcdonc authored
      webob.exc.WSGIHTTPException (convenience).
    
    - Use ``exc.message`` in docs rather than ``exc.args[0]`` now that
      we control this.
  2. Chris McDonough

    - Copy exception templates from webob.exc into pyramid.httpexceptions…

    mcdonc authored
    … and
    
      ensure they all work.
  3. Chris McDonough

    - Base exception response content type again on accept header.

    mcdonc authored
    - The ``pyramid.httpexceptions`` classes named ``HTTPFound``,
      ``HTTPMultipleChoices``, ``HTTPMovedPermanently``, ``HTTPSeeOther``,
      ``HTTPUseProxy``, and ``HTTPTemporaryRedirect`` now accept ``location`` as
      their first positional argument rather than ``detail``.  This means that
      you can do, e.g. ``return pyramid.httpexceptions.HTTPFound('http://foo')``
      rather than ``return
      pyramid.httpexceptions.HTTPFound(location='http//foo')`` (the latter will
      of course continue to work).
Commits on Jun 14, 2011
  1. Chris McDonough

    garden:

    mcdonc authored
  2. Chris McDonough

    - New method named ``pyramid.request.Request.is_response``. This method

    mcdonc authored
      should be used instead of the ``pyramid.view.is_response`` function, which
      has been deprecated.
    
    - Deprecated ``pyramid.view.is_response`` function in favor of (newly-added)
      ``pyramid.request.Request.is_response`` method.  Determining if an object
      is truly a valid response object now requires access to the registry, which
      is only easily available as a request attribute.  The
      ``pyramid.view.is_response`` function will still work until it is removed,
      but now may return an incorrect answer under some (very uncommon)
      circumstances.
  3. Chris McDonough

    garden

    mcdonc authored
Commits on Jun 13, 2011
  1. Chris McDonough

    - Remove IResponder abstraction in favor of more general IResponse

    mcdonc authored
      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.
Commits on Jun 11, 2011
  1. Chris McDonough

    todo

    mcdonc authored
  2. Chris McDonough

    todo

    mcdonc authored
  3. Chris McDonough

    - Pyramid now expects Response objects to have a __call__

    mcdonc authored
      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.
Commits on May 16, 2011
  1. Chris McDonough

    - Added API docs for ``pyramid.httpexceptions.abort`` and

    mcdonc authored
      ``pyramid.httpexceptions.redirect``.
    
    - Added "HTTP Exceptions" section to Views narrative chapter including a
      description of ``pyramid.httpexceptions.abort``; adjusted redirect section
      to note ``pyramid.httpexceptions.redirect``.
    
    - A default exception view for the context ``webob.exc.HTTPException`` (aka
      ``pyramid.httpexceptions.HTTPException``) is now registered by default.
      This means that an instance of any exception class imported from
      ``pyramid.httpexceptions`` (such as ``HTTPFound``) can now be raised from
      within view code; when raised, this exception view will render the
      exception to a response.
    
    - New functions named ``pyramid.httpexceptions.abort`` and
      ``pyramid.httpexceptions.redirect`` perform the equivalent of their Pylons
      brethren when an HTTP exception handler is registered.  These functions
      take advantage of the newly registered exception view for
      ``webob.exc.HTTPException``.
    
    - The Configurator now accepts an additional keyword argument named
      ``httpexception_view``.  By default, this argument is populated with a
      default exception view function that will be used when an HTTP exception is
      raised.  When ``None`` is passed for this value, an exception view for HTTP
      exceptions will not be registered.  Passing ``None`` returns the behavior
      of raising an HTTP exception to that of Pyramid 1.0 (the exception will
      propagate to middleware and to the WSGI server).
Commits on May 15, 2011
  1. Chris McDonough

    garden

    mcdonc authored
Commits on May 14, 2011
  1. Chris McDonough

    garden

    mcdonc authored
Something went wrong with that request. Please try again.