| Age | Commit message (Collapse) | Author |
|---|
|
Conflicts:
pyramid/configuration.py
|
|
|
|
|
|
|
|
documentation chapter (explain turning a module into a package).
|
|
Context Variables
<http://www.makotemplates.org/docs/runtime.html#context-variables>`_ for
its meaning.
- Depend on Mako 0.3.6+ (we now require the ``strict_undefined`` feature).
|
|
|
|
``mako.default_filters``, and ``mako.imports`` settings into lists.
- The Mako renderer did not properly convert the ``mako.error_handler``
setting from a dotted name to a callable.
- The Mako renderer now accepts a resource specification for
``mako.module_directory``.
|
|
simplejson from django.utils.
|
|
+ which defaults to the empty string.
|
|
is active for every view unless the view names a specific renderer).
|
|
chapter (has ``implementation()`` method, required to be used when getting
at Chameleon macros).
|
|
``pyramid_routesalchemy`` template.
|
|
- ``pyramid_alchemy``, ``pyramid_routesalchemy``, and ``pylons_sqla`` paster
templates now use idiomatic SQLAlchemy configuration in their respective
``.ini`` files and Python code.
|
|
(``AssertionError: 'SomeProject' != 'someproject'``). This is fixed.
|
|
Shootout and Virginia sample applications, ported from their repoze.bfg
origin packages.
|
|
|
|
|
|
|
|
if the import that failed was unrelated to the import requested via a
dotted name when resolving dotted names (such as view dotted names).
|
|
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 ``/``.
|
|
path)`` or ``pyramid.traversal.traverse(path)`` when ``path`` is
(erroneously) a Unicode object. The user is meant to pass these APIs a
string object, never a Unicode object. In practice, however, users indeed
pass Unicode. Because the string that is passed must be ASCII encodeable,
now, if they pass a Unicode object, its data is eagerly converted to an
ASCII string rather than being passed along to downstream code as a
convenience to the user and to prevent puzzling second-order failures from
cropping up (all failures will occur within ``pyramid.traversal.traverse``
rather than later down the line as the result of calling
``traversal_path``).
|
|
be 1.7.4).
|
|
URLs. Calling ``route_path`` is the same as calling
``pyramid.url.route_url`` with the argument ``_app_url`` equal to the empty
string.
- Add a ``pyramid.request.Request.route_path`` API. This is a convenience
method of the request which calls ``pyramid.url.route_url``.
|
|
warnings generated by Twill).
|
|
have a SessionFactory abstraction which competes with it, and maintaining
documentation on both ways to do it is a distraction.
|
|
from working.
|
|
|
|
``pyramid.zcml.file_configure``.
- The ``pyramid.testing.zcml_configure`` API has been removed. It had been
advertised as removed since 1.2a1, but hadn't actually been.
|
|
``pyramid.threadlocals.get_registry().settings`` instead or use the
``settings`` attribute of the registry available from the request
(``request.registry.settings``).
|
|
``pyramid.chameleon_zpt`` of ``get_renderer``, ``get_template``,
``render_template``, and ``render_template_to_response``.
|
|
|
|
|
|
``mako.default_filters``, and ``mako.imports``.
|
|
|
|
and ``lookup``. ``Lookup`` will be an instance of a lookup class which
supplies (late-bound) arguments for debug, reload, and translate. Any
third-party renderers which use (the non-API) function
``pyramid.renderers.template_renderer_factory`` will need to adjust their
implementations to obey the new callback argument list. This change was to
kill off inappropriate use of threadlocals.
|
|
a ``registry`` attribute on the ZCML context (kill off use of
threadlocals).
|
|
--------
- The ``settings`` object which used to be available only when
``request.settings.get_settings`` was called is now available as
``registry.settings`` (e.g. ``request.registry.settings`` in view code).
Deprecations
------------
- Obtaining the ``settings`` object via
``registry.{get|query}Utility(ISettings)`` is now deprecated. Instead,
obtain the ``settings`` object via the ``registry.settings`` attribute. A
backwards compatibility shim was added to the registry object to register
the settings object as an ISettings utility when ``setattr(registry,
'settings', foo)`` is called, but it will be removed in a later release.
- Obtaining the ``settings`` object via ``pyramid.settings.get_settings`` is
now deprecated. Obtain it as the ``settings`` attribute of the registry
now (obtain the registry via ``pyramid.threadlocal.get_registry`` or as
``request.registry``).
|
|
``pyramid_routesalchemy`` paster template.
|
|
``route_url``. These are simple passthroughs for their respective
functions in ``pyramid.url``.
- Documented the ``matchdict`` and ``matched_route`` attributes of the
request object in the Request API documentation.
|
|
|
|
pyramid.request.Request. Each is set to None.
|
|
(``your_app_secret_string``) for the ``session.secret`` setting in the
generated ``development.ini``. This was a security risk if left unchanged
in a project that used one of the templates to produce production
applications. It now uses a randomly generated string.
|
|
|
