Somehow this PR is taking longer to build, I assume from somehow missing
the build cache.

Assuming that it's a caching issue, bump up the time to satisfy un-cached builds.
If build times continue to increase we will run into this problem again (can only
regenerate the cache with a successful build but a successful build needs the cache),
but this will let us defer it a bit longer :)  Travis-CI builds are max 120 minutes.

since we were installing it from the LLVM APT repo, which they
took down since it was getting too expensive.  I guess we can
just run with the gcc build until that situation gets resolved.

exec, input: if globals has no __builtins__ add it as a dictwrapper

update list of failing cpython tests

Bump version numbers

Some packaging / distributing updates

before we added a it as a module which made code fail
which does something like __builtins__["unicode"]

Switch to CPython's descrobject.c

The behavior changed in CPython 2.7.4, and Travis-CI runs 2.7.3.

until I realize that it's because we were passing more tests than we expected.

Create a simple Dockerfile

This is for adding a guard on a non-immortal object, since we need
to be safe against that object getting deallocated and a different object
is allocated in its spot.

We had support for this already, but it leaked memory.  The biggest was
that we never freed our runtimeICs, so if those ended up getting any GC
references in them, then we would leak memory.  So I started freeing those,
but then that exposed the issue that the ICInvalidators expect that their
dependent ICs never get freed.  So I added back a mapping from ICSlotInfo->
ICInvalidators that reference them.

via their descrobject.c

Not using it in this commit, just wanted to
get the unmodified version in so it's easier to see the changes.

We were doing a "call bumpUse() early" optimization to free up registers
when we can, but as a side-effect it looked to the refcounter like the
reference was done being used.

The problem is that we emit an llvm "unreachable" instruction, and then
continue to emit other code, which fails the verifier.

endBlock(DEAD) is supposed to be the right way to handle that, but there
is some more work that would need to be done there to get that working
properly.

So just do the easy thing for now -- create a new BB so that it's ok to
emit more code.

PyObject_New: register the type if the type is not yet registered

that is just based off of pulling our latest release

str: use tp_as_sequence instead of tp_as_number

string is special in that it is a c++ type which has tp_as_number and tp_as_sequence.
This causes problems because when we fixup the slot dispatcher we will set the tp_as_number fields but not the
tp_as_sequence because setting both can cause problems.
Some extensions (e.g. numpy) require that we use the sq_* functions instead of nb_*.
Therefore clear the tp_as_number fields (except nb_remainder which cpython has set too because it is not part of
tp_as_sequence).

BoxIteratorGeneric call PyIter_Next() lazily

update virtualenv to the one which always sets zip_safe=False

We were fetching to eagerly which caused issues if the iterator got used for other stuff too

Update test results

Merge conflict between my pr that added the full test suite and Sun's that
fixed one of the tests.

Some work on the numpy test suite

[WIP] Some minor numpy fixing.