Edward George

> Why do we need compatibility with the javascript's Number.MAX_SAFE_INTEGER? this doesn't add compatibility with that at all. it only increases the width to longs to support version numbers greater...

hi, thanks for this addition, i'll take a look and merge when I next get a moment.

Undoubtably this is something that would be useful. I left this one as I thought the entire source could do with a bit of re-org to make this feature fit...

Sorry, I don't think I got/saw a notification email for this issue. I'll see if I can reproduce and dig into what's going on.

weirdly, I can't reproduce this. ``` ➜ ~ virtualenv-clone .virtualenvs/test1 .virtualenvs/test2 ➜ ~ workon test2 ➜ ~ pip uninstall nose Uninstalling nose: /Users/edwardgeorge/.virtualenvs/test2/bin/nosetests [...] Proceed (y/n)? y Successfully uninstalled nose...

virtualenvwrapper versions tested were `==4.1.1`, `==4.2`, and `==3.4`

thanks. is that rmtree safe? could we be deleting things that may not be replaced by the `fix_local_scheme` call? would it be safer to iterate through the symlinks in local...

hey, let me take a look. thanks

can you just explain the motivation for this? what would you pass in as `original_dir` and when would that be desirable? is this for when you've copied a virtualenv to...

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...