- PR is done, fixes #236

Signed-off-by: Cody Taylor <codemister99@yahoo.com>

dogpile, "generic"
- stress dogpile a bit more in caching docs

related to #234

related to #234

related to #234

- changelog for pullreq bitbucket:11

- drop python 2.4, 2.5 support
- various pep8ing

would not be correctly interpreted in Python 3.

Conflicts:
	doc/build/changelog.rst

would not be correctly interpreted in Python 3.

when a "try/except" targeted a tuple of exception types, rather
than a single exception. fixes #227

of the source file which includes parseable information about the
templates' source file, encoding etc. as well as a mapping of module
source lines to template lines, thus replacing the "# SOURCE LINE"
markers throughout the source code.  The structure also indicates those
lines that are explicitly not part of the template's source; the goal
here is to allow integration with coverage tools.

- move CHANGES to changelog.rst

- try to get all our CSS in one place and above RTD so we get all their styles...

Using "-*- encoding:utf-8 -*-" doesn't really set the file encoding
for Emacs. It will even prompt the user when opening a compiled file:

  The local variables list in foo.mak.py
  contains values that may not be safe (*).

  Do you want to apply it?  You can type
  y  -- to apply the local variables list.
  n  -- to ignore the local variables list.

  !  -- to apply the local variables list, and permanently mark these
        values (*) as safe (in the future, they will be set automatically.)

    * encoding: utf-8

The problem is that Emacs looks for a file variable named "coding" and
it doesn't know about "encoding":

  http://www.gnu.org/software/emacs/manual/html_node/emacs/Specify-Coding.html

This is no doubt why Python recognizes "coding:" by itself:

  http://www.python.org/dev/peps/pep-0263/

This change makes the code generator output "# -*- coding:%s -*-" and
updates the documentation and examples to match this style.

  method, as this method has a specific internal use. The purpose
  of Context.kwargs has been clarified, in that it only delivers
  top level keyword arguments originally passed to template.render().
  [ticket:219]