[Python-modules-team] Bug#752467: Bug#752467: (no subject)

Brian May brian at microcomaustralia.com.au
Mon Nov 17 22:39:04 UTC 2014

On 18 November 2014 07:53, Barry Warsaw <barry at 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 at aquitard:~$ django-admin    # run as sh; autodetect python
brian at aquitard:~$ python2 /usr/bin/django-admin    # force python 2
brian at 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 <brian at microcomaustralia.com.au>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20141118/476ab77f/attachment.html>

More information about the Python-modules-team mailing list