gouzounakis at hotmail.com
Thu Jul 25 15:48:09 CEST 2013
Im using windows 7 64bit
I have installed python 3.3.2 in C:\Python33
and then easy_install , pip, and virtualenv.
But i do not know if the virtualenv installation is correct as i cant seem to be able to create any virtual enviroment yet.
How can i check if everything is correct? What exactly should i do to create a virtual enviroment into my new_project folder located here: in C:\new_project ?
I think there is something wrong with the installation because when i run through idle the virtual-env scripts located in "C:\Python33\Scripts" then i get the following..
Python 3.3.2 (v3.3.2:d047928ae3f6, May 16 2013, 00:06:53) [MSC v.1600 64 bit (AMD64)] on win32
Type "copyright", "credits" or "license()" for more information.
>>> ================================ RESTART ================================
You must provide a DEST_DIR
Usage: virtualenv-3.3-script.py [OPTIONS] DEST_DIR
--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
--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 (default)
Give access to the global site-packages dir to the
--always-copy Always copy files rather than symlinking
--unzip-setuptools Unzip Setuptools when installing it
--relocatable Make an EXISTING virtualenv environment relocatable.
This fixes up scripts and makes all .pth files
--no-setuptools Do not install setuptools (or pip) in the new
--no-pip Do not install pip in the new virtualenv.
Directory to look for setuptools/pip distributions in.
You can add any number of additional --extra-search-
--never-download Never download anything from the network. This is now
always the case. The option is only retained for
backward compatibility, and does nothing. Virtualenv
will fail if local distributions of setuptools/pip are
--prompt=PROMPT Provides an alternative prompt prefix for this
--setuptools Backward compatibility. Does nothing.
--distribute Backward compatibility. Does nothing.
Traceback (most recent call last):
File "C:\Python33\Scripts\virtualenv-3.3-script.py", line 9, in <module>
load_entry_point('virtualenv==1.10', 'console_scripts', 'virtualenv-3.3')()
File "C:\Python33\lib\site-packages\virtualenv.py", line 786, in main
plz any help appreciated
More information about the Python-list