…yramid application runing under Python 3, you might have received a ``TypeError: unorderable types: function() < function()`` exception.
predicate was used in any route, the router would raise an exception when trying to print the route debugging information. This bug has existed since 1.3a1. - When the ``traverse`` predicate was used in any route, ``proutes`` and ``pviews`` console scripts would raise an exception when trying to print the route debugging information. This bug has existed since 1.3a1.
… contain colons. #629
… see c9888fc
``pyramid.security.effective_principals`` would unconditionally return the empty list. This was incorrect, it should have unconditionally returned ``[Everyone]``, and now does.
…it of the debug toolbar, which effectively requires it to be present to work properly.
app's environ will no longer have (deprecated and potentially misleading) ``bfg.routes.matchdict`` or ``bfg.routes.route`` keys in it.
… in all 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>``.
…o longer in the API docs. It was meant to be a private method; its publication in the documentation as an API method was a mistake, and it has been renamed to something private.
Configurator was an old-style ``pyramid.configuration.Configurator`` instance.