pyramid - Pyramid web framework (fork of https://github.com/Pylons/pyramid).

Age	Commit message (Collapse)	Author
2015-12-08	update narrative docs and literalinclude source files that use the starter ↵	Steve Piercy
	scaffold to reflect its current state
2014-11-25	Include code examples for integration and functional tests in docs #1001	Matt Russell
	Wrap lines as per convention.
2014-01-03	modified MyProject src	Blaise Laflamme

2013-09-05	update the MyProject example app to use pyramid_chameleon	Michael Merickel

2013-03-04	fix #311	Tshepang Lekhonkhobe

2012-11-29	Sync MyProject files with the starter scaffold	Patricio Paez
	- Line numbers are mentioned only in the Creating a Pyramid Project chapter; those that are affected were updated.
2012-01-02	have sample scaffold depend on waitress	Chris McDonough

2011-10-06	remove all reference to the paster command-line utility	Chris McDonough

2011-08-22	fix stray inclusion of weberror; move manifest description	Chris McDonough

2011-08-09	fix project.rst to deal with scaffold changes	Chris McDonough

2010-11-10	fix project chapter to deal with paster template changes	Chris McDonough

2010-11-04	fix project documentation to account for starter paster template changes	Chris McDonough

2010-10-25	convert narrative docs to Pyramid	Chris McDonough

2010-01-18	Prep for b1	Chris McDonough
	Merge a bunch of paper-based docs fixes Configure logging during bfgshell.
2009-11-10	Templates	Chris McDonough
	--------- - Remove ``ez_setup.py`` and its import from all paster templates, samples, and tutorials for ``distribute`` compatibility. The documentation already explains how to install virtualenv (which will include some ``setuptools`` package), so these files, imports and usages were superfluous. Deprecations ------------ - The ``options`` kw arg to the ``repoze.bfg.router.make_app`` function is deprecated. In its place is the keyword argument ``settings``. The ``options`` keyword continues to work, and a deprecation warning is not emitted when it is detected. However, the paster templates, code samples, and documentation now make reference to ``settings`` rather than ``options``. This change/deprecation was mainly made for purposes of clarity and symmetry with the ``get_settings()`` API and dicussions of "settings" in various places in the docs: we want to use the same name to refer to the same thing everywhere.
2008-08-24	Second checkin using StudlyCaps version of MyProject.	Chris McDonough