| Age | Commit message (Collapse) | Author |
|---|
|
|
|
from ``scan``).
|
|
|
|
|
|
package to relative ones, to reduce brittleness, eg when the user names the
package something other than 'tutorial'.
- make imports relative
- use plain relative URLs for resources (like stylesheets and images) in
page templates.
This is the last batch of this kind of change that I know about. I've
exercised the changes (via the browser and the test target) in a package
with an alternate name, 'zodbtutorial', as well as in a package with the
default name, 'tutorial'.
|
|
|
|
package to relative ones, to reduce brittleness, eg when the user names the
package something other than 'tutorial'.
- make imports relative
- use plain relative URLs for resources (like stylesheets and images) in
page templates.
|
|
package to relative ones, to reduce brittleness, eg when the user names the
package something other than 'tutorial'.
- make imports relative
- use plain relative URLs for resources (like stylesheets and images) in
page templates.
|
|
|
|
|
|
and narrative docs.
- Break out awkward description of PasteDeploy entry points from
project chapter into its own Paste chapter.
|
|
than the ``repoze.zodbconn`` package to provide ZODB integration.
- The ZODB scaffold now uses the ``pyramid_zodbconn`` package rather than the
``repoze.zodbconn`` package to provide ZODB integration.
|
|
``resource_url``, ``static_url``, and ``current_route_url`` methods of the
request rather than the function variants imported from ``pyramid.url``.
|
|
package at all; configuration in the ``production.ini`` file which used to
require its ``error_catcher`` middleware has been removed. Configuring
error catching / email sending is now the domain of the ``pyramid_exclog``
package (see https://docs.pylonsproject.org/projects/pyramid_exclog/dev/).
|
|
|
|
|
|
|
|
|
|
|
|
use ``/projects/pyramid/current`` rather than ``/projects/pyramid/dev``.
|
|
|
|
|
|
method which implements the WSGI application interface
instead of the three webob attrs status, headerlist
and app_iter. Backwards compatibility exists for
code which returns response objects that do not
have a __call__.
- pyramid.response.Response is no longer an exception
(and therefore cannot be raised in order to generate
a response).
- Changed my mind about moving stuff from pyramid.httpexceptions
to pyramid.response. The stuff I moved over has been moved
back to pyramid.httpexceptions.
|
|
|
|
pyramid.response
|
|
- New section in the main index
- Move Model and View tests there
- Added Functional tests
|
|
|
|
|
|
templates (retry ZODB conflict errors which occur in normal operations).
|
|
|
|
|
|
older version of sphinx which doesnt respect tab-width)
|
|
templates for the benefit of folks who cutnpaste and save to a non-UTF8
format.
|
|
effective logging level of WARN, which prevents e.g. SQLAlchemy statement
logging and other inappropriate output.
- The ``production.ini`` of the ``pyramid_routesalchemy`` and
``pyramid_alchemy`` paster templates did not have a ``sqlalchemy`` logger
section, preventing ``paster serve production.ini`` from working.
- The ``pyramid_routesalchemy`` and ``pyramid_alchemy`` paster templates used
the ``{{package}}`` variable in a place where it should have used the
``{{project}}`` variable, causing applications created with uppercase
letters e.g. ``paster create -t pyramid_routesalchemy Dibbus`` to fail to
start when ``paster serve development.ini`` was used against the result.
See https://github.com/Pylons/pyramid/issues/#issue/107
Closes #107
|
|
|
|
https://github.com/Pylons/pyramid/issues#issue/95
Closes issue #95.
|
|
|
|
|
|
|
|
|
|
any overly long lines in the PDF rendering.
Changes to .rst files:
(docs/tutorials/wiki/authorization.rst)
(docs/tutorials/wiki/definingviews.rst)
(docs/tutorials/wiki2/authorization.rst)
(docs/tutorials/wiki2/definingviews.rst)
1. For included templates, added :tab-width: 2 options.
2. wiki2/authorization.rst: Wrong markup for file names __init__.py and
views.py just after the subhead "Adding security.py".
Changes to .py files: Folded a few long lines.
(docs/tutorials/wiki/src/basiclayout/tutorial/views.py)
(docs/tutorials/wiki/src/authorization/tutorial/views.py)
(docs/tutorials/wiki/src/views/tutorial/views.py)
(docs/tutorials/wiki2/src/basiclayout/tutorial/models.py)
(docs/tutorials/wiki2/src/models/tutorial/models.py)
Changes to .pt files: Broke long lines; reformatted for 2-space
indentation using tabs.
(docs/tutorials/wiki/src/authorization/tutorial/templates/edit.pt)
(docs/tutorials/wiki/src/authorization/tutorial/templates/login.pt)
(docs/tutorials/wiki/src/authorization/tutorial/templates/view.pt)
(docs/tutorials/wiki/src/views/tutorial/templates/edit.pt)
(docs/tutorials/wiki/src/views/tutorial/templates/view.pt)
(docs/tutorials/wiki2/src/authorization/tutorial/templates/edit.pt)
(docs/tutorials/wiki2/src/authorization/tutorial/templates/login.pt)
(docs/tutorials/wiki2/src/authorization/tutorial/templates/view.pt)
(docs/tutorials/wiki2/src/views/tutorial/templates/edit.pt)
(docs/tutorials/wiki2/src/views/tutorial/templates/view.pt)
|
|
|
|
|
|
--------
- ``pyramid.testing.setUp`` and ``pyramid.testing.tearDown`` have been
undeprecated. They are now the canonical setup and teardown APIs for test
configuration, replacing "direct" creation of a Configurator. This is a
change designed to provide a facade that will protect against any future
Configurator deprecations.
Paster Templates
----------------
- All paster templates now use ``pyramid.testing.setUp`` and
``pyramid.testing.tearDown`` rather than creating a Configurator "by hand"
within their ``tests.py`` module, as per decision in features above.
Documentation
-------------
- The wiki and wiki2 tutorials now use ``pyramid.testing.setUp`` and
``pyramid.testing.tearDown`` rather than creating a Configurator "by hand",
as per decision in features above.
- The "Testing" narrative chapter now explains ``pyramid.testing.setUp`` and
``pyramid.testing.tearDown`` instead of Configurator creation and
``Configurator.begin()`` and ``Configurator.end()``.
|
|
|
|
wiki tutorial
|
|
|
|
request.static_url('{{package}}:static/foo.css') instead of ${request.application_url}/static/foo.css for static files
|
|
|
|
is based on scanning.
- Changed the "ZODB + Traversal Wiki Tutorial" based on changes to
``pyramid_zodb`` Paster template.
|
