| Age | Commit message (Collapse) | Author |
|
``DBSession`` instead (this is more common in real SQLA apps).
|
|
This is not permitted due to error reporting requirements, and a better
error message is shown when it is attempted. Previously it would fail with
something like "AttributeError: 'NoneType' object has no attribute
'rfind'".
Fixed #420.
|
|
converted to a response (for example, when a view callable returns a
dictionary without a renderer defined, or doesn't return any value at all).
The error message now contains information about the view callable itself
as well as the result of calling it.
|
|
--------
- The ``scan`` method of a ``Configurator`` can be passed an ``ignore``
argument, which can be a string, a callable, or a list consisting of
strings and/or callables. This feature allows submodules, subpackages, and
global objects from being scanned. See
http://readthedocs.org/docs/venusian/en/latest/#ignore-scan-argument for
more information about how to use the ``ignore`` argument to ``scan``.
Dependencies
------------
- Depend on ``venusian`` >= 1.0a3 to provide scan ``ignore`` support.
|
|
|
|
|
|
allowing them to find their way into resolveConflicts).
|
|
|
|
``includeme``. See https://github.com/Pylons/pyramid/pull/392.
Closes #392.
|
|
|
|
return HTML or text. See https://github.com/Pylons/pyramid/issues/381
Fixes #381.
|
|
flag when the ``development.ini`` file (any any other .ini file in use) is
changed. See https://github.com/Pylons/pyramid/issues/377 and
https://github.com/Pylons/pyramid/pull/411
Fixes #377.
|
|
|
|
|
|
``Configurator.add_view`` that pointed to a class with a ``view_defaults``
decorator, the view defaults would not be applied. See
https://github.com/Pylons/pyramid/issues/396 .
Fixes #396.
|
|
|
|
a ``wsgi.file_wrapper`` (see
http://www.python.org/dev/peps/pep-0333/#optional-platform-specific-file-handling)
when one is provided by the web server.
|
|
|
|
|
|
``request.upath_info`` (Unicode) rather than ``request.path_info``
(indeterminate value based on Python 3 vs. Python 2). This has to be done
to normalize matching on Python 2 and Python 3.
|
|
more than one view relied on the defaults being different for configuration
conflict resolution. See https://github.com/Pylons/pyramid/issues/394.
Closes #394.
|
|
|
|
|
|
config.add_route('trav_route', 'traversal/{traverse:.*}')
Would cause a ``UnicodeDecodeError`` when the route was matched and the
matched portion of the URL contained any high-order characters. See also
https://github.com/Pylons/pyramid/issues/385 .
|
|
|
|
as a decorator with no arguments like this::
@subscriber()
def somefunc(event):
pass
Would register ``somefunc`` to receive all events sent via the registry,
but this was untrue. Instead, it would receive no events at all. This has
now been fixed and the code matches the documentation. See also
https://github.com/Pylons/pyramid/issues/386
Closes #386
|
|
|
|
|
|
|
|
e.g. ``adapters.lookup(...).__discriminator__(context, request)``. It will
be used by superdynamic systems that require the discriminator to be used
for introspection after manual view lookup.
|
|
docs. It survives on in the Cookbook
(http://docs.pylonsproject.org/projects/pyramid_cookbook/en/latest/gae.html).
Rationale: it provides the correct info for the Python 2.5 version of GAE
only, and this version of Pyramid does not support Python 2.5.
|
|
"Command-Line Pyramid" chapter.
|
|
(``pviews``, ``proutes``, etc).
|
|
|
|
|
|
want to have extension scaffolds that can work across Pyramid 1.0.X, 1.1.X,
1.2.X and 1.3.X. See the new "Creating Pyramid Scaffolds" chapter in the
narrative documentation for more info.
- Added an API docs chapter for ``pyramid.scaffolds``.
- Added a narrative docs chapter named "Creating Pyramid Scaffolds".
- The ``template_renderer`` method of ``pyramid.scaffolds.PyramidScaffold``
was renamed to ``render_template``. If you were overriding it, you're a
bad person, because it wasn't an API before now. But we're nice so we're
letting you know.
|
|
handling of --list-templates
|
|
whatsnew.
|
|
|
|
``pyramid.path.DottedNameResolver``. The former can be used to resolve
asset specifications, the latter can be used to resolve dotted names to
modules or packages.
|
|
|
|
|
|
deprecated since Pyramid 1.0, and was never an API.
|
|
|
|
using another WSGI server; random docs fixes
|
|
|
|
|
|
|
|
|
|
|