assertion error on clone

[bioinformed]

I have a fairly heavy VE with several dozen packages installed. When I attempt to clone, the following assertion failure is shown, where remaining==[u'2.7']. Is this a show-stopper or can it be safely ignored?

kjacobs@0-compute:~/projects/locus-ve/0.0.1$ time bin/virtualenv-clone . ../clone3
Traceback (most recent call last):
File "bin/virtualenv-clone", line 9, in
load_entry_point('virtualenv-clone==0.2.4', 'console_scripts', 'virtualenv-clone')()
File "/locus/home/kjacobs/projects/locus-ve/0.0.1/local/lib/python2.7/site-packages/clonevirtualenv.py", line 268, in main
clone_virtualenv(old_dir, new_dir)
File "/locus/home/kjacobs/projects/locus-ve/0.0.1/local/lib/python2.7/site-packages/clonevirtualenv.py", line 89, in clone_virtualenv
assert not remaining, _virtualenv_sys(dst_dir)
AssertionError: (u'2.7', [u'/locus/home/kjacobs/projects/locus-ve/0.0.1/local/lib/python2.7/site-packages/pip-1.2.1-py2.7.egg', u'/locus/home/kjacobs/projects/locus-ve/0.0.1/local/lib/python2.7/site-packages/locus_ve-0.0.1-py2.7.egg', u'/locus/home/kjacobs/projects/locus-ve/0.0.1/lib/python2.7/site-packages/pip-1.2.1-py2.7.egg', u'/locus/home/kjacobs/projects/locus-ve/0.0.1/lib/python2.7/site-packages/locus_ve-0.0.1-py2.7.egg', u'/locus/home/kjacobs/projects/locus-ve/0.0.1/lib/python2.7', u'/locus/home/kjacobs/projects/locus-ve/0.0.1/lib/python2.7/plat-linux2', u'/locus/home/kjacobs/projects/locus-ve/0.0.1/lib/python2.7/lib-tk', u'/locus/home/kjacobs/projects/locus-ve/0.0.1/lib/python2.7/lib-old', u'/locus/home/kjacobs/projects/locus-ve/0.0.1/lib/python2.7/lib-dynload', u'/usr/lib/python2.7', u'/usr/lib/python2.7/plat-linux2', u'/usr/lib/python2.7/lib-tk', u'/locus/home/kjacobs/projects/locus-ve/0.0.1/local/lib/python2.7/site-packages', u'/locus/home/kjacobs/projects/locus-ve/0.0.1/local/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg-info', u'/locus/home/kjacobs/projects/locus-ve/0.0.1/lib/python2.7/site-packages', u'/locus/home/kjacobs/projects/locus-ve/0.0.1/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg-info'])

[edwardgeorge]

hmm, /locus/home/kjacobs/projects/locus-ve/0.0.1/ is the location of the source virtualenv you're cloning from? it looks like there are items in the target virtualenv's sys.path still pointing to the original virtualenv, in fact it looks like it's running from the original location entirely. I would say that is a show-stopper!

if you run the python in the new, cloned virtualenv and print out sys.path what does it print? ie: ../clone3/bin/python -c "import sys; print sys.path"

also, if you run virtualenv-clone with the -v argument, what does it output?