| Age | Commit message (Collapse) | Author |
|
|
|
|
|
``accept`` predicate in a Pyramid application runing under Python 3, you
might have received a ``TypeError: unorderable types: function() <
function()`` exception.
|
|
- Add ``add_subscriber_predicate`` method to Configurator.
- Allow ``add_subscriber`` and ``subscriber`` venusian decorator to accept ``**predicates`` arguments.
- Document subscriber predicate feature.
- Share more code between view, route, and subscriber related method wrt predicates.
|
|
|
|
|
|
|
|
|
|
https://github.com/Pylons/pyramid/pull/661
|
|
|
|
in-the-wild code they're not totally confused); we'll remove it later
|
|
|
|
directive registers a free-standing permission introspectable into the
Pyramid introspection system. Frameworks built atop Pyramid can thus use
the the ``permissions`` introspectable category data to build a
comprehensive list of permissions supported by a running system. Before
this method was added, permissions were already registered in this
introspectable category as a side effect of naming them in an ``add_view``
call, this method just makes it possible to arrange for a permission to be
put into the ``permissions`` introspectable category without naming it
along with an associated view. Here's an example of usage of
``add_permission``::
config = Configurator()
config.add_permission('view')
|
|
|
|
|
|
|
|
|
|
a given request due to predicates not working), the exception now contains
a textual description of the predicate which didn't match.
- Fixes issue #502 and issue #519.
|
|
``view_config`` decorator caused a ``RuntimeError: dictionary changed size
during iteration`` exception. It no longer does. See
https://github.com/Pylons/pyramid/issues/635 for more information.
- Fixes issue #635.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(this time for sure)
|
|
|
|
|
|
|
|
|
|
imply that ``HEAD`` is implied when you use ``GET``. For example, using
``@view_config(request_method='GET')`` is equivalent to using
``@view_config(request_method='HEAD')``. Using
``@view_config(request_method=('GET', 'POST')`` is equivalent to using
``@view_config(request_method=('GET', 'HEAD', 'POST')``. This is because
HEAD is a variant of GET that omits the body, and WebOb has special support
to return an empty body when a HEAD is used.
|
|
|
|
|
|
``pyramid.security.effective_principals`` would unconditionally return the
empty list. This was incorrect, it should have unconditionally returned
``[Everyone]``, and now does.
|
|
|
|
- Fork point: master now represents a future 1.4 release.
|
|
|
|
the debug toolbar, which effectively requires it to be present to work
properly.
|
|
|
|
it possible for instance methods to be used as view callables) introduced a
backwards incompatibility when methods that declared only a request
argument were used. See https://github.com/Pylons/pyramid/issues/503
Fixes #503
|
|
|
|
app's environ will no longer have (deprecated and potentially misleading)
``bfg.routes.matchdict`` or ``bfg.routes.route`` keys in it.
|
|
|
|
|
|
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.
|
|
- The ``alchemy`` scaffold now shows an informative error message in the
browser if the person creating the project forgets to run the
initialization script.
- The ``alchemy`` scaffold initialization script is now called
``initialize_<projectname>_db`` instead of ``populate_<projectname>``.
|
|
``__text__``. See https://github.com/Pylons/pyramid/issues/461
Fixes #461.
|
|
|