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!

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...

This is so that we can add the CAPI slots for things like tp_as_sequence,
so that C extensions will work properly.

I don't think there are very many extensions that would do this but let's
still support it for now; it further bloats the type objects but only as
much as it does in CPython as well.

Previously had hardcoded three different iterations.

- Start moving towards slotdefs
- add tp_repr support
- add an slots_tester extension module so we can test these more narrowly

Move some type-related stuff into typeobject.cpp or descrobject.cpp

Separated out from some more involved changes that are
required to get the 'pwd' module working.

Haven't added structseq.c to the build quite yet

Remove some definitions that should no longer be in there
(structs for which we have Pyston-internal definitions).

Instead of doing "typedef void PyIntObject", do
"struct _PyIntObject; typedef struct _PyIntObject PyIntObject;"
which prevents spurious things like type conversions or
sizeof(void)'s.

I'm not sure that we need to do this at the expression-level --
I think we just have to do it at the statement level.