[use_latest_valgrind] Use valgrind-3.10.0
Fix a GC bug

We were scanning the wrong number of bytes for conservative objects;
we were using the allocated size instead of the user size, but
starting the scan at the beginning of the user section.

Finally ran into a case where a conservative object was the very
last object in the heap and it segfaulted.
Set pypa option for not handling future import errors

Signed-off-by: Vinzenz Feenstra <evilissimo@gmail.com>
Astprint improvements

Signed-off-by: Vinzenz Feenstra <evilissimo@gmail.com>
Fix assert in very verbose mode
Merge pull request #212 from lyh-kernel/use_latest_valgrind

[use_latest_valgrind] Use valgrind-3.10.0
Refactor: move BoxedClass from core/ to runtime/
Refactor: abstract this functionality more
Fix slicing issues
In addition:
 * unify slicing
 * performance improvements, especially for string slicing
fix memory leak
Add repr ics and refactor things slightly
Merge pull request #219 from undingen/mem_leak

fix memory leak
Merge pull request #214 from vinzenz/astprint-improvements

Astprint improvements
Merge pull request #215 from vinzenz/pypa-future-handling

Set pypa option for not handling future import errors
Merge pull request #217 from undingen/llvm_assert

Fix assert in very verbose mode
Merge pull request #218 from undingen/fix_slice

Fix slicing issues
List slice-self-assignment is currently buggy

Not sure how hard a requirement it is to match CPython's behavior,
but just assert out for now rather than doing something different.

Also add an assert to copySlice, which could have similar issues.
Minor: call this _doFree helper from this other path
Fix uninitiated read of >> 3 == 3 (REPL)
Merge pull request #223 from lyh-kernel/pyston-191

Fix uninitiated read of >> 3 == 3 (REPL)