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

Cmake add pwdmodule, slots_test, and match existing test configurations

fixes #238 CMake issues

We weren't able to exit if we had a thread running in the background,
since we released the GIL at the end of the C level main() and the
background thread would start running again after all the data structures
had been torn down.

Now, just keep holding the GIL as we exit.

Was tired of seeing bare "unimplemented" error messages and having
to track down where they were coming from -- especially tricky
when trying to add fork() support and the errors were in the child.

- int(bool) works
- hash(bool) works
- str.find() now takes an optional "start" parameter

- Set the import "level" appropriately (takes absolute_import flag into account)
- Add a basic implementation of the __import__() function
- Fix a bug in existing import behavior (would not check sys.modules in certain
  cases)

ie running setup.py under Pyston.

Doesn't work yet, but (in a separate branch) was able to hack up
the distutils library until it did!

-these should now be skipped for python < 2.7.4, not >= 2.7.4
-check-pyston now passes on ubuntu 12.04 (including travis-ci.org) and 14.04

-now we only build the parts of llvm that are actually required

I thought we weren't going to be able to do it since posixmodule.c
is 9kloc, but it's working!

Had to make one modification to posixmodule.c where it was directly
accessing the fd of a file object; haven't figured out the best way
to handle this.

Should probably reorganize/rename the "lib_python" directory at some point.

Somehow had gotten the C API definitions of True and False backwards...