Not sure if this is really a good feature for users, but taking
command line arguments from an environment variable is definitely
helpful for testing things like virtualenv which spawns a number (~10)
of subprocess.

Stats

Misc stuff for pycrypto

cuts down time to JIT 'pip' from 115ms to 65ms

this speeds up pip by several seconds because the pyston executable is very large.
CPython does not run into the problem because of the much smaller executable but has the same problem
when it has to retrieve the libc version of the pyston executable

support for 3arg pow, long("0xBB", 16) and long("0xBBL", 0)

bcrypt support

- Py_FatalError() has to be an expression (previously was multi-line macro)
- Add definitions of some PyObject_GC_* functions
- imp.load_dynamic

With these changes, bcrypt installs and runs

Amazingly, cffi compiled just fine with some missing function
declarations.  It provided implicit definitions for them and
then casted the "int" return type up to a PyObject*.

Some misc virtualenv + library support

(dependencies of bcrypt)
Increase test timeouts since this takes around 90s to install
in debug mode.

Base off of sys.prefix instead of sys.executable, since in
virtualenvs the executable is in an extra bin/ directory.

But not both cmp and key at the same time.
We might want to just switch to CPython's sort implementation for that.

Remove a workaround in req_install.py

Rewrite calls into BoxedMethodDescriptors

This involves
- special-casing their __get__
- adding some ability to rewrite calls to functions that take *args

initial compile() support

Hopefully this helps detect more forms of file corruption,
such as 0-byte cache files.

Modules have a __file__ attribute but that's only used for
the module repr.  The filename that's used in tracebacks
is stored in the code object.

We don't currently destruct CLFunctions, but this makes it
clear that each SourceInfo belongs to a single CLFunction.

compile() is starting to work

Before, if we saw that they were going to immediately be executed in
the current globals scope (ie no "in" clause), we would execute them
without custom globals.

In order to split the compilation from the execution, just always
compile them with custom globals support.  This involved some refactoring
of the assumptions about when the globals object gets passed or not.