Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Jun 22, 2011
  1. @mcdonc

    garden

    mcdonc authored
Commits on Jun 20, 2011
  1. @mcdonc

    - 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. @mcdonc

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

    mcdonc authored
    … and
    
      ensure they all work.
  3. @mcdonc

    - 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. @mcdonc

    garden:

    mcdonc authored
  2. @mcdonc

    - 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. @mcdonc

    garden

    mcdonc authored
Commits on Jun 13, 2011
  1. @mcdonc

    - 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. @mcdonc

    todo

    mcdonc authored
  2. @mcdonc

    todo

    mcdonc authored
  3. @mcdonc

    - 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. @mcdonc

    - 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. @mcdonc

    garden

    mcdonc authored
Commits on May 14, 2011
  1. @mcdonc

    garden

    mcdonc authored
Commits on May 13, 2011
  1. @mcdonc

    good enough

    mcdonc authored
  2. @mcdonc

    - The ``add_route`` method of the Configurator now accepts a ``static``

    mcdonc authored
      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.
  3. @mcdonc

    - Added documentation for a "multidict" (e.g. the API of ``request.PO…

    mcdonc authored
    …ST``) as
    
      interface API documentation.
Commits on May 12, 2011
  1. @mcdonc
  2. @mcdonc

    garden

    mcdonc authored
Commits on Apr 22, 2011
  1. @mcdonc

    garden

    mcdonc authored
Commits on Apr 19, 2011
  1. @mcdonc

    garden

    mcdonc authored
  2. @mcdonc

    garden

    mcdonc authored
Commits on Apr 18, 2011
  1. @mcdonc

    garden

    mcdonc authored
  2. @mcdonc

    garden

    mcdonc authored
Commits on Apr 13, 2011
  1. @mcdonc
Commits on Apr 12, 2011
  1. @mcdonc

    request.response

    mcdonc authored
Commits on Apr 10, 2011
  1. @mcdonc

    gardening

    mcdonc authored
  2. @mcdonc

    - It is now possible to get information about why Pyramid raised a Fo…

    mcdonc authored
    …rbidden
    
      exception from within an exception view.  The ``ACLDenied`` object returned
      by the ``permits`` method of each stock authorization policy
      (``pyramid.interfaces.IAuthorizationPolicy.permits``) is now attached to
      the Forbidden exception as its ``result`` attribute.  Therefore, if you've
      created a Forbidden exception view, you can see the ACE, ACL, permission,
      and principals involved in the request as
      eg. ``context.result.permission``, ``context.result.acl``, etc within the
      logic of the Forbidden exception view.
  3. @mcdonc

    garden

    mcdonc authored
  4. @mcdonc

    gardening

    mcdonc authored
  5. @mcdonc

    rocky added i18n to jinja2

    mcdonc authored
  6. @mcdonc

    - An exception raised by a NewRequest event subscriber can now be cau…

    mcdonc authored
    …ght by
    
      an exception view.
Commits on Mar 25, 2011
  1. @mcdonc
Commits on Mar 21, 2011
  1. @mcdonc

    note promise

    mcdonc authored
Commits on Feb 1, 2011
  1. @mcdonc

    garden

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