On 18 November 2014 07:53, Barry Warsaw <ba...@debian.org> wrote: > The typical solution is to move the /usr/bin script (and manpage, etc.) > into a > separate binary package, and it makes the most sense to call this > 'virtualenv'. Because /usr/bin/virtualenv is a Python 3 script, it > Depends on > python3-virtualenv. There are use cases for keeping python-virtualenv as a > separate Python 2-compatible library that would e.g. be importable. >
For another solution, have a look at django-admin, provided by the django-common package. You can call it using any of the following ways: brian@aquitard:~$ django-admin # run as sh; autodetect python brian@aquitard:~$ python2 /usr/bin/django-admin # force python 2 brian@aquitard:~$ python3 /usr/bin/django-admin # force python 3 That way it works if only python-django is installed and it also works if only python3-django is installed. The ability to force a particular version of python may not be so useful for virtualenv however. -- Brian May <br...@microcomaustralia.com.au>
