Bug#754248: Just a note

2014-07-17 Thread jb
This affects me too. Regrettably some of us still need to use and develop
systems based on legacy python versions, having virtualenv working with old
python versions is important.

Problem might be related to the fact that virtualenv command now uses
python3 by default.

which virtualenv
/usr/bin/virtualenv

cat /usr/bin/virtualenv
#! /usr/bin/python3
# EASY-INSTALL-ENTRY-SCRIPT:
'virtualenv==1.11.6','console_scripts','virtualenv'
__requires__ = 'virtualenv==1.11.6'
import sys
from pkg_resources import load_entry_point

if __name__ == '__main__':
sys.exit(
load_entry_point('virtualenv==1.11.6', 'console_scripts',
'virtualenv')()
)

JB


Bug#754248: Just a note

2014-07-17 Thread Scott Kitterman
On Thursday, July 17, 2014 21:15:07 jb wrote:
 This affects me too. Regrettably some of us still need to use and develop
 systems based on legacy python versions, having virtualenv working with old
 python versions is important.

But unrelated to if virtualenv is using python or python3 as it's runtime.  It 
still support python virtual environments (modulo bugs such as this one).

Scott K

signature.asc
Description: This is a digitally signed message part.