to not conflict with CPython's -O.  They're quite similar
(increase optimization level), but some tests ask for -O when
they don't really want our version of it.

Main difference is lowering the recursion-depth on unoptimized
builds, since we need more stack space per python frame.

We symlink the CPython tests into our tests directory to control which
ones we will attempt to run.  A bunch of the tests though need other
test files in order to run, and we hadn't symlinked those in.

At some point we should switch to symlinking the Lib/test directory instead
of individual files, but for now this helps.

[WIP]Let GCC 5 happy and update the CPython test notes

Be able to run an unmodified virtualenv

These cpython tests are working now

Which are quite hard to reproduce because they depend on the details
of the C stack.

Anyway, we should probably start using the recursion-depth-tracking functions
in more place, rather than getting segfaults.  There are a lot of CPython tests
that test for recursion-depth-checking.

Fix some corner cases in the irgen refcounter, and fix a refcount
issue in the bz2 module itself.

Do it by patching distutils, which setuptools I guess builds on

Well, really an unmodified pip+setuptools

The last piece is py_compile.  Just shim that back into our parser
to get the parser to write out a pyc file.

It seems like we don't even need this -- most callers of py_compile
(or at least, virtualenv), don't seem to care if the compile step
passed or failed.  But while we're here, try to support it.

Switch to CPython way to build standard C extensions.

Merge AST/BST work into master

AST: deallocate nodes

Use a bumpptr allocator to keep track of the AST nodes.
I could not use the LLVM one because it does not call the destructor on allocated elements.

AST & BST: remove unnecessary nodes and fields + little less memory usage

Disable some extensions, part of because they were handled by
from_cpython/CMakefile.txt, part of beacuase we need to enable it in
seperated PR. Such as tk extension.

And also add some modifications to let extension can find the source
code in correct path.

Some minor improvements from the metaserver branch

We mostly did a good job of picking flags that CPython doesn't use (or at least, that
its manpage doesn't advertise), but there are a couple that need to be changed.

One is for TRAP which is a feature I don't even remember anymore, so that's removed.

The other is for stats -- '-s' is now changed to '-T'.  This will be annoying to change
on the perf-tracking side.

This reverts commit 111ca525.

BST: a bytecode-like AST

And make BST_arguments a bit safer by removing misleading fields.

And remove some extraneous things from bst

fix a bug where compare could ignore CAPI exceptions and add _heapq

A bunch of function metadata refactorings