simplify

  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]

  interpreted correctly within a template tag.  [ticket:190]

  skips over module elements that are not explcitly callable,
  avoiding TypeError when trying to produce partials.
  [ticket:207]

- guess this is 0.9.0

- add more of a test

Without this change, when running setup.py extract_messages, we would get
error:

    TokenError: ('EOF in multi-line statement', (2, 0))

Looking at the unit test, it seems like a literal string argument in the form
of "_('xxx')" is supposed to be picked up by Babel. However, that contradicts
with the documentation, which states:

> When using tags, the values of the arguments are taken as literal strings by
> default. To embed Python expressions as arguments, use the embedded
> expression format

So, as a side effect of this commit, the convenience of "_('xxx')" has been
removed. Probably can add it back if necessary for backward compatibility.

  if Python version is < 2.6 or is between 3.0 and
  less than 3.3, as Markupsafe now only supports 2.6->2.X,
  3.3->3.X. [ticket:216]

  converted for py3k properly (added tests.)
  [ticket:214]

  file warnings when running the tests under
  various Pythons with warnings turned on.
  [ticket:213]

  compatible with Py3k.  [ticket:212]

so that inheritance chains and includes are located
correctly, [ticket:202]

- add gpg sig

  against a module compiled to the filesystem would
  fail trying to produce a RichTraceback due to the
  content being in bytes. [ticket:209]

  from tuple to frozenset, as this is expected to be
  a set by default.  [ticket:208]

- fix test_exceptions to always call non-pygments tests
- update test for py3k transition

  TemplateLookup, allows alternate Lexer classes
  to be used.

waiting on further detail what I'm missing here

- dont need 2to3
- clean up some list() calls we dont need

having some weird unicode issues I can't debug; the meaning of
str.encode() seems to be changing globally somehow

- changelog