Change-Id: Idd64b63b4498590fb5d4ba906dc477fdf34b3e4b

Change-Id: I664df7a926a0bf90c46e8d43c5fb2468aa42578d

Change-Id: Ifd065e96676fde5429fd3d5f27c59c960e1ac6bb

This works like error_handler but is specific to a template
when included in another using the include tag.

Change-Id: Ie5506a8cba42c71519c703eacc82050902b9ceba
Pull-request: https://bitbucket.org/zzzeek/mako/pull-requests/22

Change-Id: Ib357002b0c919ce532c9b67ba40fcee91ba2554c

Change-Id: I05fcaaebe4566093894fc6abdee705c955ec4a09

in 161b1cf5

As reported upstream in sphinx:
https://github.com/sphinx-doc/sphinx/pull/2396

It was a structural change in sphinx-1.4. I'm not sure if this is the
proper fix, but it does let the doc build pass, in my testing.

Originally reported at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830178

.

Signed-off-by: Nishanth Aravamudan <nish.aravamudan@canonical.com>

- upgrade tox file to use py35, coverage, etc.
- add flake8 rules

changes in pygments formatting; we might be losing
a bit of what was tested here originally but we still assert pygments
is taking place.

This allows the lexer to correctly handle strings like:
    ${'backslash quote right-curly is \\\'}'}

And also allows users to use the bitwise-or operator to mean bitwise or
simply by enclosing the expression inside parens:
    ${(0x5432 | 0x8000)}

or by using it in the middle of a dictionary literal:
    ${ {'foo-val': 0x43 | 0x100, 'bar-val': 0x22 | 0x100}[thing+'-val']}

or inside brackets:
    ${ big_lookup_dict[index_low | (indexhigh << 3)] }

Basically, only "top level" uses of the vertical bar mean pipe.

(Note that currently, any non-top-level use of the vertical bar in
an expression just results in a syntax error in the generated python,
so no working code is affected by this change)

If mako templates contain something like "_('Köln')", babel extractor converts
it to pure ASCII so that resulting .po file would contain "K\xf6ln". Not all
translation tools and translations are ready for such kind of escape sequences.

Babel allows message ids to be non-ascii, the plugin just has to return Unicode
objects instead of ASCII strings (and that's exactly how Babel built-in Python
and JavaScript extractors work).

This fix ensures mako extractor doesn't excape non-ascii symbols, works well
both for Unicode and non-unicode input (there is a test for cp1251 encoding),
and also provides a workaround for babel charset detector python-babel/babel#274.

- posixpath.join does not handle windows paths very well.

Now all tests pass on py27 & py34 on windows.

* add all deps to tox
* ignore test products

we removed universal wheels from setup.cfg.   The bigger change
in this issue will need to be revisited fully for hopefully
the next release

additionally replace the use of ``inspect.getargspec()`` under
Python 3 (seems to be called from the TG plugin) to avoid deprecation
warnings.
fixes #250