| Age | Commit message (Collapse) | Author |
|
- Added "Finding a Resource With a Class or Interface in Lineage" to
Resources narrative chapter.
|
|
chapter.
- Added "Determining if a Resource is In The Lineage of Another Resource" to
Resources narrative chapter.
|
|
--------
- If a resource implements a ``__resource_url__`` method, it will be called
as the result of invoking the ``pyramid.url.resource_url`` function to
generate a URL, overriding the default logic. See the new "Generating The
URL Of A Resource" section within the Resources narrative chapter.
Documentation
-------------
- Added "Generating The URL Of A Resource" section to the Resources narrative
chapter (includes information about overriding URL generation using
``__resource_url__``).
- Added "Generating the Path To a Resource" section to the Resources
narrative chapter.
- Added "Finding a Resource by Path" section to the Resources narrative
chapter.
|
|
|
|
|
|
|
|
documentation.
|
|
|
|
|
|
prefixed with ``PYRAMID_`` (e.g. ``BFG_DEBUG_NOTFOUND`` is now
``PYRAMID_DEBUG_NOTFOUND``)
|
|
exception now shows the decorator information that caused the conflict.
- Depend on Venusian >= 0.5 (for scanning conflict exception decoration).
|
|
|
|
|
|
|
|
|
|
chapter.
|
|
default. It is the application registry object.
- Changed "Project" chapter slightly to expand on use of ``paster pshell``.
|
|
|
|
--------
- Added ``debug_routematch`` configuration setting that logs matched routes
(including the matchdict and predicates).
Documentation
-------------
- Added "Debugging Route Matching" section to the urldispatch narrative
documentation chapter.
- Added reference to ``BFG_DEBUG_ROUTEMATCH`` envvar and ``debug_routematch``
config file setting to the Environment narrative docs chapter.
|
|
|
|
|
|
|
|
|
|
at ``pyramid_traversalwrapper`` instead).
|
|
instruct you to run a test which would fail because the view callable
generated by the ``pyramid_zodb`` tutorial used a one-arg view callable,
but the test in the sample code used a two-arg call.
- Updated ZODB+Traversal tutorial setup.py of all steps to match what's
generated by ``pyramid_zodb``.
|
|
assumed UNIX path segments in filenames).
|
|
|
|
|
|
The symptoms were: lots of deprecation warnings printed to the console
about imports of deprecated Pyramid functions and classes and non-detection
of views decorated with ``view_config`` decorators. This has now been
fixed. Closes #68.
|
|
|
|
|
|
were required to pass a ``package`` argument although ``package`` is not
actually required. If you didn't pass ``package``, you would receive an
error something like ``KeyError: '__name__'`` emanating from the
``pyramid.path.caller_module`` function. This has now been fixed.
|
|
|
|
``pyramid.configuration.add_handler``.
|
|
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.
|