Creating virtualenvs from a virtualenv always yells at me

[Julian]

Creating a virtualenv from within a virtualenv (on PyPy only?) always spits out spurious Path not in prefix warnings, that appear to come from https://github.com/pypa/virtualenv/blob/master/virtualenv.py#L1087.

Functionally, everything appears fine, and from reading the surrounding code their quickly, it seems like the warning is incorrect in this case (and that the next block of code is going to find the correct value), but it's difficult to tell.

Reproducer:

~/Desktop
⊙  rm -rf foo bar && pypy ~/Development/virtualenv/virtualenv.py --quiet foo && echo "DONE" && foo/bin/pypy ~/Development/virtualenv/virtualenv.py --quiet bar                                                                                                                                                                                              Julian@Macnetic
DONE
Path not in prefix '/Users/Julian/Desktop/foo/include' '/usr/local/Cellar/pypy/6.0.0/libexec'

[gaborbernat]

@Julian can you provide a test that exhibits this as a PR?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just add a comment if you want to keep it open. Thank you for your contributions.

[Julian]

Missed that comment but yeah sure could probably turn that bash into a test fairly easily.

[gaborbernat]

This is becoming obsolete with #1366 now in full swing.