Permalink
Commits on Jun 20, 2011
  1. prep for 1.1a1

    mcdonc committed Jun 20, 2011
  2. bring whatsnew up to date

    mcdonc committed Jun 20, 2011
  3. bring whatsnew up to date

    mcdonc committed Jun 20, 2011
  4. - Register the default exception view for context of

    mcdonc committed Jun 20, 2011
      webob.exc.WSGIHTTPException (convenience).
    
    - Use ``exc.message`` in docs rather than ``exc.args[0]`` now that
      we control this.
  5. - Copy exception templates from webob.exc into pyramid.httpexceptions…

    mcdonc committed Jun 20, 2011
    … and
    
      ensure they all work.
  6. coverage

    mcdonc committed Jun 20, 2011
  7. - Base exception response content type again on accept header.

    mcdonc committed Jun 20, 2011
    - 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 19, 2011
  1. fix rendering

    mcdonc committed Jun 19, 2011
Commits on Jun 14, 2011
  1. we no longer support 2.4

    mcdonc committed Jun 14, 2011
  2. merge httpexception-utils branch

    mcdonc committed Jun 14, 2011
  3. garden:

    mcdonc committed Jun 14, 2011
  4. - Move default app_iter generation logic into __call__ for

    mcdonc committed Jun 14, 2011
      exception responses.
    
    - Add note about why we've created a shadow exception hierarchy
      parallel to that of webob.exc.
  5. - New method named ``pyramid.request.Request.is_response``. This method

    mcdonc committed Jun 14, 2011
      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.
  6. - Added new add_response_adapter method to Configurator.

    mcdonc committed Jun 14, 2011
    - Fix Configurator docstring wrt exception responses.
    
    - Speed up registry.queryAdapterOrSelf
  7. garden

    mcdonc committed Jun 14, 2011
  8. render nicer docs

    mcdonc committed Jun 14, 2011
  9. flesh out IResponse interface

    mcdonc committed Jun 14, 2011
Commits on Jun 13, 2011
  1. name argument makes no sense here

    mcdonc committed Jun 13, 2011
  2. - Remove IResponder abstraction in favor of more general IResponse

    mcdonc committed Jun 13, 2011
      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. todo

    mcdonc committed Jun 11, 2011
  2. todo

    mcdonc committed Jun 11, 2011
  3. - Pyramid now expects Response objects to have a __call__

    mcdonc committed Jun 11, 2011
      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 Jun 7, 2011
  1. Merge pull request #209 from Cito/master

    cguardia committed Jun 7, 2011
    Signed the contributor agreement.
  2. Signed the contributor agreement.

    Cito committed Jun 7, 2011
  3. Fix for issue 208.

    cguardia committed Jun 7, 2011
  4. Merge pull request #207 from wichert/master

    mcdonc committed Jun 7, 2011
    Language fallback support
Commits on Jun 6, 2011