Looks like for now this only changes double-closing-angle-brackets
(now formats "> >" as ">>" in templates), but apparently it has
effects on raw string literals as well.

Starting to really hit critical mass in terms of having enough
API support that it's easier to copy additional API functions over.

And turn off that part of the fork.py test as well

My first stab at writing CMake rules

Required a small amount of object changes, and then a large
number of replacements where we directly compared the class
to int_cls.  We now check that it's a subclass, since you
are allowed to use True/False anywhere that you could use
an int.  ex "xrange(0, n, step=True)"

in both directions, from Pyston->CAPI and CAPI->Pyston

Otherwise those symbols don't end up getting exported and things
crash if we try to do any inlining, which only happens on the larger
benchmarks or when running in -O mode.

travis run full ninja check-pyston and update README

As much as I don't like modifying the standard libraries,
removing the dependence on this particular one helps a lot,
since it (indirectly) imports weakref which will take a while
for us to support.

ie by running 'make check USE_CMAKE=1'

changed:
- defer to cmake for building the unittests
- building extensions doesn't use the rest of the build system so can remove
  that unnecessary dependency (would cause an llvm build otherwise).

Should also reduce our Linux-dependence

I was surprised that Py_BEGIN_ALLOW_THREADS was working, but it turns
out that we weren't enabling threading so it wasn't doing anything.

Compiling posixmodule.c under ccache in certain systems ends up
causing trouble.

fixes #4 add travis-ci.org support