| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
in the hybrid example. Confirm this is correct XXX
|
|
|
|
|
|
paragraph about losing POST data on redirect to a warning
|
|
|
|
|
|
|
|
|
|
|
|
- ``pyramid_alchemy``, ``pyramid_routesalchemy``, and ``pylons_sqla`` paster
templates now use idiomatic SQLAlchemy configuration in their respective
``.ini`` files and Python code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
tutorials and paster templates (no longer required).
|
|
|
|
|
|
|
|
the route pattern instead of ``:marker``. The old syntax is still backwards
compatible and accepted. The new format allows a regular expression for that
marker location to be used instead of the default ``[^/]+``, for example
``{marker:\d+}`` is now valid to require the marker to be digits.
|
|
|
|
|
|
|
|
|
|
in the pattern, instead of immediately following a ``/``.
- Added ``marker_pattern`` option to ``add_route`` to supply a dict of
regular expressions to be used for markers in the pattern instead of the
default regular expression that matched everything except a ``/``.
|
|
|
|
|
|
(After a recursive grep for ':[a-z]*:`[A-Z0-9a-z._]*``')
|
|
the implication a bit confusing"
|
|
``pyramid.threadlocals.get_registry().settings`` instead or use the
``settings`` attribute of the registry available from the request
(``request.registry.settings``).
|
|
|
|
``mako.default_filters``, and ``mako.imports``.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|