The cloned env is linked to the original

[ka7eh]

I tried the package that comes with Ubuntu 16.04, i.e. version 0.2.5, and I'm seeing an unexpected behavior. Whatever changes I make in a cloned environment reflects in the original too.

Here's an example:

$ mkvirtualenv venv_a
(venv_a)$ pip install django==1.11.7
(venv_a)$ pip freeze
	Django==1.11.7
	pytz==2017.3

$ virtualenv-clone /path/to/venv_a /path/to/venv_b
$ workwon venv_b
(venv_b)$ pip freeze
	Django==1.11.7
	pytz==2017.3
(venv_b)$ pip install django==1.8.7
(venv_b)$ pip freeze
	Django==1.8.7
	pytz==2017.3

At this point I expect vevn_a to be on Django 1.11.7 and venv_b on Django 1.8.7. But when I switch to venv_a, I see it's changed too:

$ workon venv_a
(venv_a)$ pip freeze
	Django==1.8.7
	pytz==2017.3

[ka7eh]

Tested wit the latest version too (0.2.6) and still end up with the same result.

[jgwinner]

Jumping on, this seems like a killer