| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
renderers), let the configurator figure out what to do with various paths and resource specs
|
|
|
|
|
|
resource spec.
|
|
|
|
|
|
|
|
``pyramid.configuration.Configurator.add_view`` method, or the
``pyramid.view.view_config`` decorator (nee ``bfg_view``) is no longer
permitted to be one of the strings ``GET``, ``HEAD``, ``PUT``, ``POST`` or
``DELETE``, and now must always be an interface. Accepting the
method-strings as ``request_type`` was a backwards compatibility strategy
servicing repoze.bfg 1.0 applications. Use the ``request_method``
parameter instead to specify that a view a string request-method predicate.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
update the startup chapter to show them
|
|
|
|
|
|
|
|
|
|
``pyramid_routesalchemy`` paster template.
|
|
|
|
|
|
|
|
``pyramid_zodb`` paster template.
|
|
|
|
wiki tutorial
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Paster templates no longer contain a ``run`` module; setup code is
in __init__.
- {{package}}.ini is now always development.ini
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit 20fbdee307e554c2cd44c54fb7860a0ca0a8e19b.
|
|
This reverts commit 96d7897c0bc86c25afb861fb2ee61d5e4351b0dc.
|
|
|