| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
- Normalize the Seeing our changes section
- Changed import to recommended style
|
|
- Sync content of Add login and logout views,
Add the login.pt template, Return a logged_in
flag, Add a logout link sections
- Normalize sections of views.py
|
|
- Sync content in Adding Authentication and
Authorization policies, Add permission
declarations sections
- Added mising permission=view in SQL tutorial
- Moved __init__.py listing to Seeing our changes
|
|
Pyramid-provided ``.ini`` files. This setting previously told Chameleon to
render better exceptions; now Chameleon always renders nice exceptions
regardless of the value of this setting.
Fixes #491.
|
|
wrapper for ``pyramid.Config.configurator.add_view`` which does the right
thing about permissions. It should be preferred over calling ``add_view``
directly with ``context=HTTPForbidden`` as was previously recommended.
- New API: ``pyramid.view.forbidden_view_config``. This is a decorator
constructor like ``pyramid.view.view_config`` that calls
``pyramid.config.Configurator.add_forbidden_view`` when scanned. It should
be preferred over using ``pyramid.view.view_config`` with
``context=HTTPForbidden`` as was previously recommended.
- Updated the "Creating a Not Forbidden View" section of the "Hooks" chapter,
replacing explanations of registering a view using ``add_view`` or
``view_config`` with ones using ``add_forbidden_view`` or
``forbidden_view_config``.
- Updated all tutorials to use ``pyramid.view.forbidden_view_config`` rather
than ``pyramid.view.view_config`` with an HTTPForbidden context.
|
|
lines in order to be able to tell people to comment out only the
``pyramid_debugtoolbar`` line when they want to disable the toolbar.
|
|
issue #398)
|
|
|
|
|
|
from ``scan``).
|
|
|
|
|
|
package to relative ones, to reduce brittleness, eg when the user names the
package something other than 'tutorial'.
- make imports relative
- use plain relative URLs for resources (like stylesheets and images) in
page templates.
This is the last batch of this kind of change that I know about. I've
exercised the changes (via the browser and the test target) in a package
with an alternate name, 'zodbtutorial', as well as in a package with the
default name, 'tutorial'.
|
|
|
|
package to relative ones, to reduce brittleness, eg when the user names the
package something other than 'tutorial'.
- make imports relative
- use plain relative URLs for resources (like stylesheets and images) in
page templates.
|
|
package to relative ones, to reduce brittleness, eg when the user names the
package something other than 'tutorial'.
- make imports relative
- use plain relative URLs for resources (like stylesheets and images) in
page templates.
|
|
|
|
|
|
and narrative docs.
- Break out awkward description of PasteDeploy entry points from
project chapter into its own Paste chapter.
|
|
than the ``repoze.zodbconn`` package to provide ZODB integration.
- The ZODB scaffold now uses the ``pyramid_zodbconn`` package rather than the
``repoze.zodbconn`` package to provide ZODB integration.
|
|
``resource_url``, ``static_url``, and ``current_route_url`` methods of the
request rather than the function variants imported from ``pyramid.url``.
|
|
package at all; configuration in the ``production.ini`` file which used to
require its ``error_catcher`` middleware has been removed. Configuring
error catching / email sending is now the domain of the ``pyramid_exclog``
package (see https://docs.pylonsproject.org/projects/pyramid_exclog/dev/).
|
|
|
|
|
|
|
|
|
|
|
|
use ``/projects/pyramid/current`` rather than ``/projects/pyramid/dev``.
|
|
|
|
|
|
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.
|
|
|
|
pyramid.response
|
|
- New section in the main index
- Move Model and View tests there
- Added Functional tests
|
|
|
|
|
|
templates (retry ZODB conflict errors which occur in normal operations).
|
|
|
|
|
|
older version of sphinx which doesnt respect tab-width)
|
|
templates for the benefit of folks who cutnpaste and save to a non-UTF8
format.
|
|
effective logging level of WARN, which prevents e.g. SQLAlchemy statement
logging and other inappropriate output.
- The ``production.ini`` of the ``pyramid_routesalchemy`` and
``pyramid_alchemy`` paster templates did not have a ``sqlalchemy`` logger
section, preventing ``paster serve production.ini`` from working.
- The ``pyramid_routesalchemy`` and ``pyramid_alchemy`` paster templates used
the ``{{package}}`` variable in a place where it should have used the
``{{project}}`` variable, causing applications created with uppercase
letters e.g. ``paster create -t pyramid_routesalchemy Dibbus`` to fail to
start when ``paster serve development.ini`` was used against the result.
See https://github.com/Pylons/pyramid/issues/#issue/107
Closes #107
|
|
|
|
https://github.com/Pylons/pyramid/issues#issue/95
Closes issue #95.
|
|
|
|
|
