| Age | Commit message (Collapse) | Author |
|
|
|
- Added more indexing markers to sections in documentation.
|
|
|
|
|
|
|
|
http://stackoverflow.com/questions/6703850/cant-get-pyramid-to-work-with-mod-wsgi
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Renamed make_request to _make_request to make clear that it's not a
private API.
p.scripting.prepare now raises an exception if no valid pyramid app can
be found to avoid obscure errors later on.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
chapter.
|
|
Configurator when describing global_registries, add http_cache newness warning
|
|
|
|
- change prepare return value to a dict, and return the registry,
request, etc
- various docs and changelog entries.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
deprecated ``pyramid.view.static`` class. ``pyramid.satic.static_view`` by
default serves up documents as the result of the request's ``path_info``,
attribute rather than it's ``subpath`` attribute (the inverse was true of
``pyramid.view.static``, and still is). ``pyramid.static.static_view``
exposes a ``use_subpath`` flag for use when you don't want the static view
to behave like the older deprecated version.
- The ``pyramid.view.static`` class has been deprecated in favor of the newer
``pyramid.static.static_view`` class. A deprecation warning is raised when
it is used. You should replace it with a reference to
``pyramid.static.static_view`` with the ``use_subpath=True`` argument.
|
|
|
|
|
|
|
|
configuration file value ``prevent_http_cache``. These are synomymous and
allow you to prevent HTTP cache headers from being set by Pyramid's
``http_cache`` machinery globally in a process. see the "Influencing HTTP
Caching" section of the "View Configuration" narrative chapter and the
detailed documentation for this setting in the "Environment Variables and
Configuration Settings" narrative chapter.
- New documentation section in View Configuration narrative chapter:
"Influencing HTTP Caching".
|
|
inappropriately used ``DBSession.rollback()`` instead of
``transaction.abort()`` in one place.
- Wiki2 (SQLAlchemy + URL Dispatch) tutorial ``models.initialize_sql`` didn't
match the ``pyramid_routesalchemy`` scaffold function of the same name; it
didn't get synchronized when it was changed in the scaffold.
|
|
route to be added without an intermediate ``config.commit()``. If you now
receive a ``ConfigurationError`` at startup time that appears to be
``add_route`` related, you'll need to either a) ensure that all of your
route names are unique or b) call ``config.commit()`` before adding a
second route with the name of a previously added name or c) use a
Configurator that works in ``autocommit`` mode.
|
|
``__setitem__`` or ``update`` methods of the event object with a key that
already existed in the renderer globals dictionary, a ``KeyError`` was
raised. With the deprecation of the "add_renderer_globals" feature of the
configurator, there was no way to override an existing value in the
renderer globals dictionary that already existed. Now, the event object
will overwrite an older value that is already in the globals dictionary
when its ``__setitem__`` or ``update`` is called (as well as the new
``setdefault`` method), just like a plain old dictionary. As a result, for
maximum interoperability with other third-party subscribers, if you write
an event subscriber meant to be used as a BeforeRender subscriber, your
subscriber code will now need to (using ``.get`` or ``__contains__`` of the
event object) ensure no value already exists in the renderer globals
dictionary before setting an overriding value.
|
|
|
|
|
|
|