separate vim_ipython module into its own file
Py3K support. Three at last, three at last!
remove stale debugging code
ENH Start a new Ipython kernel from vim

This is a bit hacky, but it works well enough:

1. generate a new random ID
2. use the subprocess to start a completely new IPython kernel process
   with that ID. This may not even be the same Python version that vim
   is running (this is a feature, not a bug)
3. connect to this kernel

Currently, the kernel is automatically killed at exit.
use KernelManager for starting a new kernel