Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Dec 29, 2010
  1. @mcdonc

    factor deriver from mapper

    mcdonc authored
Commits on Dec 22, 2010
  1. @mcdonc
  2. @mcdonc
Commits on Nov 21, 2010
  1. @mcdonc

    - Add ``pyramid.interfaces.ITemplateRenderer`` interface to Interface…

    mcdonc authored
    …s API
      chapter (has ``implementation()`` method, required to be used when getting
      at Chameleon macros).
Commits on Nov 2, 2010
  1. @mcdonc

    - New event type: ``pyramid.interfaces.IBeforeRender``. An object of …

    mcdonc authored
    …this type
      is sent as an event before a renderer is invoked (but after the
      application-level renderer globals factory added via
      ``pyramid.configurator.configuration.set_renderer_globals_factory``, if any,
      has injected its own keys).  Applications may now subscribe to the
      ``IBeforeRender`` event type in order to introspect the and modify the set of
      renderer globals before they are passed to a renderer.  The event object
      iself has a dictionary-like interface that can be used for this purpose.  For
        from import subscriber
        from pyramid.interfaces import IRendererGlobalsEvent
        def add_global(event):
            event['mykey'] = 'foo'
      If a subscriber attempts to add a key that already exist in the renderer
      globals dictionary, a ``KeyError`` is raised.  This limitation is due to the
      fact that subscribers cannot be ordered relative to each other.  The set of
      keys added to the renderer globals dictionary by all subscribers and
      app-level globals factories must be unique.
Commits on Nov 1, 2010
  1. @mcdonc
Commits on Oct 29, 2010
  1. @mcdonc

    sessioning docs

    mcdonc authored
Commits on Oct 25, 2010
  1. @mcdonc

    convert API docs to Pyramid

    mcdonc authored
Commits on Sep 14, 2010
  1. - The ``add_route`` method of a Configurator now accepts a

    Chris McDonough authored
      ``pregenerator`` argument.  The pregenerator for the resulting route
      is called by ``route_url`` in order to adjust the set of arguments
      passed to it by the user for special purposes, such as Pylons
      'subdomain' support.  It will influence the URL returned by
      ``route_url``.  See the ``repoze.bfg.interfaces.IRoutePregenerator``
      interface for more information.
Commits on Sep 12, 2010
  1. - The BFG router now emits an additional event unconditionally at the

    Chris McDonough authored
      end of request processing:
      ``repoze.bfg.interfaces.IFinishedRequest``.  This event is meant to
      be used when it is necessary to perform unconditional cleanup after
      request processing.  See the ````
      class documentation for more information.
    - The ``repoze.bfg.interfaces.IWSGIApplicationCreatedEvent`` event
      interface was renamed to
      ``repoze.bfg.interfaces.IApplicationCreated``.  Likewise, the
      ```` class was renamed
      to ````.  The older aliases will
      continue to work indefinitely.
    - The ``repoze.bfg.interfaces.IAfterTraversal`` event interface was
      renamed to ``repoze.bfg.interfaces.IContextFound``.  Likewise, the
      ```` class was renamed to
      ````.  The older aliases will continue
      to work indefinitely.
Commits on Sep 8, 2010
  1. dont expose this until necessary

    Chris McDonough authored
  2. - The ``repoze.bfg.interfaces`` API documentation page is now rendered

    Chris McDonough authored
      via ``repoze.sphinx.autointerface``.
    - The URL Dispatch narrative chapter now refers to the ``interfaces``
      chapter to explain the API of an ``IRoute`` object.
    - ``tests_require`` now includes ``repoze.sphinx.autointerface`` as a
Commits on Aug 8, 2010
  1. - New public interface: ``repoze.bfg.exceptions.IExceptionResponse``.

    Chris McDonough authored
      This interface is provided by all internal exception classes (such
      as ``repoze.bfg.exceptions.NotFound`` and
      ``repoze.bfg.exceptions.Forbidden``), instances of which are both
      exception objects and can behave as WSGI response objects.  This
      interface is made public so that exception classes which are also
      valid WSGI response factories can be configured to implement them
      or exception instances which are also or response instances can be
      configured to provide them.
    - New API class: ``repoze.bfg.view.AppendSlashNotFoundViewFactory`` (undoes 
      previous custom_notfound_view on request passsed to 
    - Previously, two default view functions were registered at
      Configurator setup (one for ``repoze.bfg.exceptions.NotFound`` named
      ``default_notfound_view`` and one for
      ``repoze.bfg.exceptions.Forbidden`` named
      ``default_forbidden_view``) to render internal exception responses.
      Those default view functions have been removed, replaced with a
      generic default view function which is registered at Configurator
      setup for the ``repoze.bfg.interfaces.IExceptionResponse`` interface
      that simply returns the exception instance; the ``NotFound` and
      ``Forbidden`` classes are now still exception factories but they are
      also response factories which generate instances that implement the
      new ``repoze.bfg.interfaces.IExceptionResponse`` interface.
Commits on Dec 23, 2009
  1. - Added the ``repoze.bfg.authentication``,

    Chris McDonough authored
      ``repoze.bfg.authorization``, and ``repoze.bfg.interfaces`` modules
      to API documentation.
Commits on Jul 3, 2009
  1. API docs audit.

    Chris McDonough authored
Commits on Jan 12, 2009
  1. - An interface specific to the HTTP verb (GET/PUT/POST/DELETE/HEAD) is

    Chris McDonough authored
      attached to each request object on ingress.  The HTTP-verb-related
      interfaces are defined in ``repoze.bfg.interfaces`` and are
      ``IGETRequest``, ``IPOSTRequest``, ``IPUTRequest``,
      ``IDELETERequest`` and ``IHEADRequest``.  These interfaces can be
      specified as the ``request_type`` attribute of a bfg view
      declaration.  A view naming a specific HTTP-verb-matching interface
      will be found only if the view is defined with a request_type that
      matches the HTTP verb in the incoming request.  The more general
      ``IRequest`` interface can be used as the request_type to catch all
      requests (and this is indeed the default).  All requests implement
      ``IRequest``. The HTTP-verb-matching idea was pioneered by
      <>`_ . That
      package is no longer required, but still functions fine.
Something went wrong with that request. Please try again.