Package: python-virtualenv Version: 1.0-4 Severity: important
First note that I've set python2.5 as the default Python version. I installed virtualenv and expected it to create a Python 2.5 environment. But it created a Python 2.4 one. I know from other Python scripts that the shebang line has a major influence in Python paths' resolution. So I changed "/usr/bin/python2.4" to "/usr/bin/python2.5". It created a Python 2.5 environment but not the copy of the "python" binary. Hence I changed the shebang line to "/usr/bin/python" and it worked as expected. I know that the Gentoo package does the same. A more complex solution (I didn't look at the code of virtualenv) would be to create both binaries in the virtual environment. Hervé -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-virtualenv depends on: ii python 2.4.4-6 An interactive high-level object-o ii python-central 0.6.1 register and build utility for Pyt ii python-pkg-resources 0.6c8-3 Package Discovery and Resource Acc ii python-setuptools 0.6c8-3 Python Distutils Enhancements ii python2.4 2.4.5-1 An interactive high-level object-o python-virtualenv recommends no packages. -- no debconf information
