You know, when developing code, it is very tedious to look for meaningful
errors and warnings in presence of tons of noise like

    warning: deprecated conversion from string constant to ‘char*’

And you know what? It seems in the next version of gcc, this deprecation
warnings will be turned into errors.

----

Python sources already use 'const' keyword freely, so I think it's time to add
constify bits all over the place.

It appears that the machinery is all there to protect the declaration
of inconsistent linkage types (i.e. dllimport vs. dllexport) by using
a guard unique to the pyx file.  This patch simply emits that guard
for the current module to prevent the error "inconsistent linkage types"
on a Windows-based system.

Simply a typo in NextNode...

Pyrex merge: disable multiple compilation in one context, verbose mode to output file names during compilation

--HG--
rename : tests/compile/varargdecl.pyx => tests/run/varargdecl.pyx

use PyBytes_Type instead of PyString_Type in the generated sources, PyBytes fix for Py2.6, unicode fixes for star imports

Make TreeFragment.py more readable; copy substitution nodes and copy over pos attributes on substitutions

'#define PyString_Type PyBytes_Type' in Py3: 'str' is considered a builtin and internally mapped to PyString_Type, which must also work in Py3