before we only registered BSS data (aka static vars without initalizer) now we also register static vars with initalizer.
CFFI (and probably other libraries) needs this.

Add setting func.func_code, PyCFunction_Call, vars() error handling

We pass most of the tests, some of the errors are becasue we don't use refcounting and lxml depends on it (aka pypy has the same issues)

- in additon allow Py_TPFLAGS_HAVE_VERSION_TAG because even though we don't use it this flag shouldn't cause problems
- allow tp_del because AFAIK it's implemented.
- allow calling methods which specify METH_COEXIST because it doen't make a difference for the call
- disable PyCode_New call inside cython because we don't support it yet and it's unused.
- change cython to use PyCFunction_Call instead of the custom version it has for pypy

some long improvements

Enable a bunch more sqlalchemy tests

and sqlalchemy needs it to.  Disable unboxing for now; I think
I know how to reenable it but I don't think there will be much
of a perf impact.

The CPython implementation relies on immediate destruction.

some improvements in intNew

This checking should probably be enforced by the API.

Wasn't checking the return convention -- not sure how I missed this
when I added that.

Misc fixes for sqlalchemy

It would memorize whether or not to call __getattr__, and didn't do enough
guarding to make sure that that was the case.

need to free the metaclasses in the same collection.

A discrepancy between irgen and type_analysis was causing an assertion.  The
difference was that irgen will do full type inference for things that get put
into closures (ie in the parent scope), but type_analysis was bailing and
just saying that it was unknown.

Support the "decorator" library

`print >>None` goes to stdout, and printing to things without write()
functions should throw exceptions.

by converting to our DICT_BACKED hidden class strategy.

Set a flag on the class, rather than having to specify a whitelist.
Even though this is pretty annoying I think it's still worth it.

ie exec and eval statements are supposed to start with the future
flags of the scope in which they are called.  Our flags currently
get applied after parsing, which for the most part is fine, except
print_statement which actually changes the result of parsing.

ie `exec "print(1, 2)"` could either be parsed as a function call,
which will print "1 2", or as a print statement of a tuple, which
prints out "(1, 2)".  So thread the future flags through the parsing
stages as well.

Try to fix set-dtor segfault

The line of a decorated function is the decorator

This is the test for the fix in vinzenz/libpypa#49

fix Makefile to be able to 'make' after 'make clean'

The issue is that the set destructor, which is marked as "safe",
will try to access the type object.  But a safe destructor is not
allowed to assume that any objects are alive, including its own class.

We do actually force the class to be alive during a safe destructor,
but the tp_mro field was not so lucky.  We could try to address this by
saying again that types have ordered finalizers, which will cause them
to also keep their references alive.  But this doesn't completely work
since it will cause issues with objects that have actual ordered finalizers.

So for now, just remove type-check from the destructor.

Properly handle METH_COEXIST

By importing the cpython implementations of add_methods / add_members /
add_getset.

Set cls->has_getattribute for extension classes