Since app-admin/eselect-python-20090801, virtualenv only works if the path to the actual python binary is specified. This doesn't work: $ virtualenv ~/virtualenv/test New python executable in /home/sayap/virtualenv/test/bin/python ERROR: The executable /home/sayap/virtualenv/test/bin/python is not functioning ERROR: It thinks sys.prefix is '/home/sayap' (should be '/home/sayap/virtualenv/test') ERROR: virtualenv is not compatible with this system or executable This works: $ virtualenv -p /usr/bin/python2.6 ~/virtualenv/test Reproducible: Always
virtualenv should work with >=app-admin/eselect-python-20090804.
No, it doesn't work for me. machine ~ # eselect python list Available python interpreters: [1] python2.6 * machine ~ # eselect python version Version 20090804 machine ~ # virtualenv /tmp/test New python executable in /tmp/test/bin/python ERROR: The executable /tmp/test/bin/python is not functioning ERROR: It thinks sys.prefix is '/root' (should be '/tmp/test') ERROR: virtualenv is not compatible with this system or executable machine ~ # virtualenv /tmp/test -p /usr/bin/python2.6 Running virtualenv with interpreter /usr/bin/python2.6 New python executable in /tmp/test/bin/python2.6 Not overwriting existing python script /tmp/test/bin/python (you must use /tmp/test/bin/python2.6) Installing setuptools...............done.
This bug will be fixed by changes suggested in bug #281971. *** This bug has been marked as a duplicate of bug 281971 ***
