I cannot reproduce this.  First, virtualenv requires an argument, which
is the destination directory to create.  If I call it with no arguments
as you have above, I get this:


@limelight[/tmp:1003]% virtualenv
You must provide a DEST_DIR
Usage: virtualenv [OPTIONS] DEST_DIR

Options:
  --version             show program's version number and exit
  -h, --help            show this help message and exit
  -v, --verbose         Increase verbosity
  -q, --quiet           Decrease verbosity
  -p PYTHON_EXE, --python=PYTHON_EXE
                        The Python interpreter to use, e.g.,
                        --python=python2.5 will use the python2.5 interpreter
                        to create the new environment.  The default is the
                        interpreter that virtualenv was installed with
                        (/usr/bin/python)
  --clear               Clear out the non-root install and start from scratch
  --no-site-packages    Don't give access to the global site-packages dir to
                        the virtual environment
  --unzip-setuptools    Unzip Setuptools or Distribute when installing it
  --relocatable         Make an EXISTING virtualenv environment relocatable.
                        This fixes up scripts and makes all .pth files
                        relative
  --distribute          Ignored.  Distribute is used by default. See
                        --setuptools to use Setuptools instead of Distribute.
  --setuptools          Use Setuptools instead of Distribute. Set environ
                        variable VIRTUALENV_USE_SETUPTOOLS to make it the
                        default.


When I call it with a destination directory, it works fine for me:


@limelight[/tmp:1004]% virtualenv /tmp/xx
New python executable in /tmp/xx/bin/python
Please make sure you remove any previous custom paths from your 
/home/barry/.pydistutils.cfg file.
Installing 
distribute..................................................................................................................................................................................done.


This is on a machine that just yesterday I upgraded from Maverick to Natty.

Perhaps try re-installing virtualenv?  E.g.

$ sudo apt-get install --reinstall python-virtualenv


** Changed in: python-defaults (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/747590

Title:
  After upgrading to narwal virtualenv has ceased to work

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to