pylearn2 PATH variable - python

there is surprisingly little documentation or tutorials about this.
I want to run pylearn2 on my Mac OSX 10.11.1.
Acoording to the tutorial I should run at first this line:
cd pylearn/pylearn2/scripts/tutorials/grbm_smd/
python make_dataset.py
Yet the script fails with this exception:
Traceback (most recent call last):
File "/Users/username/python/pylearn2/pylearn2/utils/string_utils.py", line 53, in preprocess
else os.environ[varname])
File "/Users/username/anaconda/lib/python3.4/os.py", line 633, in __getitem__
raise KeyError(key) from None
KeyError: 'PYLEARN2_DATA_PATH'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "make_dataset.py", line 27, in <module>
train = cifar10.CIFAR10(which_set="train")
File "/Users/username/python/pylearn2/pylearn2/datasets/cifar10.py", line 71, in __init__
string_utils.preprocess('${PYLEARN2_DATA_PATH}'),
File "/Users/username/python/pylearn2/pylearn2/utils/string_utils.py", line 56, in preprocess
reraise_as(NoDataPathError())
File "/Users/username/python/pylearn2/pylearn2/utils/exc.py", line 90, in reraise_as
six.reraise(type(new_exc), new_exc, orig_exc_traceback)
File "/Users/username/anaconda/lib/python3.4/site-packages/theano/compat/six.py", line 321, in reraise
raise value.with_traceback(tb)
File "/Users/username/python/pylearn2/pylearn2/utils/string_utils.py", line 53, in preprocess
else os.environ[varname])
File "/Users/username/anaconda/lib/python3.4/os.py", line 633, in __getitem__
raise KeyError(key) from None
pylearn2.utils.exc.NoDataPathError: You need to define your PYLEARN2_DATA_PATH environment variable. If you are
using a computer at LISA, this should be set to /data/lisa/data.
Platform-specific instructions for setting environment variables:
Linux
=====
On most linux setups, you can define your environment variable by adding this
line to your ~/.bashrc file:
export PYLEARN2_VIEWER_COMMAND="eog --new-instance"
*** YOU MUST INCLUDE THE WORD "export". DO NOT JUST ASSIGN TO THE ENVIRONMENT VARIABLE ***
If you do not include the word "export", the environment variable will be set
in your bash shell, but will not be visible to processes that you launch from
it, like the python interpreter.
Don't forget that changes from your .bashrc file won't apply until you run
source ~/.bashrc
or open a new terminal window. If you're seeing this from an ipython notebook
you'll need to restart the ipython notebook, or maybe modify os.environ from
an ipython cell.
Mac OS X
========
Environment variables on Mac OS X work the same as in Linux, except you should
modify and run the "source" command on ~/.profile rather than ~/.bashrc.
Original exception:
KeyError: PYLEARN2_DATA_PATH
I inserted the following information from the exception into ~/.profile
export PYLEARN2_VIEWER_COMMAND="eog --new-instance"
and ran
source ~/.bashrc
As it still threw an exception I did some research and found out I must put the .profile file into the .bash_profile. So I added this line to .bash_profile:
#.profile
source ~/.profile
However the outcome is still the same :(
Additional information
According to the installation guide says I should add another information to the path envoirement, yet I cannot understand which in particular.
hidden files in my system
.bash_history
.bash_profile
.bash_profile-anaconda.bak
.bash_sessions
.config
.ipython
.local
.profile
.python_history
.theano
.vminfo


After going through the code myself I've found the solution. There is a bug in the sourcecode, which is missing the download_cifar10.sh script. Plus the tutorial is missing a PATH variable which is necessary.
Instruction
1.) set the PATH variable
export PYLEARN2_VIEWER_COMMAND="eog --new-instance"
export PYLEARN2_DATA_PATH=/YOURPATHTOHERE/pylearn2/datasets
2.) download cifar-10 (python version)
3.) unpack it
You will get a "cifar-10-batches-py" folder
4.) Wrap "cifar-10-batches-py" in a "cifar-10" folder
5.) Put the "cifar-10" folder into /pylearn2/datasets
The final path containing the cifar-10 files should be:
../pylearn2/datasets/cifar-10-batches-py/cifar-10
You're ready to go!


The download script exist:
https://github.com/lisa-lab/pylearn2/blob/master/pylearn2/scripts/datasets/download_cifar10.sh
Did you download Pylearn2 correctly? Did you delete files in it by mistake?

Related

Windows 10: PIL.Image.open(abc).load(xyz) triggers OSError: Unable to locate Ghostscript on paths

I'm using Python on Windows 10 with PyCharm. My script contains this line:
img = PIL.Image.open(io.BytesIO(ps.encode('utf-8')))
It triggers this error:
Traceback (most recent call last):
File "C:/Users/x/Desktop/ytg2/main.py", line 504, in <module>
generate_terrain(driver)
File "C:/Users/x/Desktop/ytg2/main.py", line 129, in generate_terrain
img = open_eps(ps, dpi=95.5)
File "C:/Users/x/Desktop/ytg2/main.py", line 32, in open_eps
img.load(scale=math.ceil(scale))
File "C:\Users\x\AppData\Local\Programs\Python\Python37\lib\site-packages\PIL\EpsImagePlugin.py", line 332, in load
self.im = Ghostscript(self.tile, self.size, self.fp, scale)
File "C:\Users\x\AppData\Local\Programs\Python\Python37\lib\site-packages\PIL\EpsImagePlugin.py", line 134, in Ghostscript
raise OSError("Unable to locate Ghostscript on paths")
OSError: Unable to locate Ghostscript on paths
Process finished with exit code 1
So what I understand is that the function load of the object returned by PIL.Image.open uses the package Ghostscript that can't be found with the interpreter.
So here is, in the order, what I've tried to do:
In PyCharm's packages manager, I've installed the following packages: python3-ghostscript and ghostscript.
In Windows 10 Environments Variables, I have added this variable: (name="Ghostscript" ; value="C:\Program Files\gs\gs9.52\bin\gswin64.exe"). Previously, I've of course manually installed Ghostscript (https://www.ghostscript.com/download/gsdnld.html). I 've tried this value too: %ProgramFiles%\gs%\gs9.52%\bin%\gswin64.exe.
However the problem is still here. What could I do?

The PIL.Image.open(io.BytesIO(ps.encode('utf-8'))) uses shutils.which('gswin64c') to find gswin64c (I knew that by clicking on a file link that the Python Interpreter shown in the PyCharm's console, in the error logs - this link is: one of the two last lines beginning with the word File in the error logs I've shown in the OP, if I remember well).
shutils.which('gswin64c') was returning None (indeed, I made myself a print of it) ; so I prompted os.environ["PATH"] and indeed, it was not contained in the printed output. Then to be sure, I typed echo %path% in the Windows 10 CLI, and I made the same constatation.
My conclusion was: I thought I was correctly adding the path of gswin64c in the way I mentionned in the OP of this SOflw Question (via the admin panel) but in fact, I was wrong.
(Maybe this step is optional.) So: first, since it doesn't work, I have deleted the path of gswin64c that I have added via the admin panel (cf.: the OP). This deletion was done via the admin panel too.
Then, to correctly add the path of gswin64c, I've typed, in the Windows CLI: setx path "%path%;c:\Program Files\..........\" (this path must contain gswin64c). Then I've restarted Windows 10 (if I remember well, it was required).
Then I re-printed the result of shutils.which('gswin64c') and gswin64c is found now. Also os.environ["PATH"] and echo %path% correctly output the path of gswin64c.
I hope this answer could help someone. In fact it was not very difficult: one just has to know how to correctly add a path on Windows 10.... Lol.
I was "inspired" by: https://www.windows-commandline.com/set-path-command-line/ ;-) .

"jupyter-kernelspec" not found while installing iqsharp however it exists on PATH

While installing QDK for use with python as described in this guide, on executing dotnet iqsharp install I get the following exception
Traceback (most recent call last):
File "c:\users\hp\appdata\local\programs\python\python36\lib\runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "c:\users\hp\appdata\local\programs\python\python36\lib\runpy.py", line 85, in _run_code
exec(code, run_globals)
File "C:\Users\hp\AppData\Local\Programs\Python\Python36\Scripts\jupyter.exe\__main__.py", line 7, in <module>
File "c:\users\hp\appdata\local\programs\python\python36\lib\site-packages\jupyter_core\command.py", line 247, in main
command = _jupyter_abspath(subcommand)
File "c:\users\hp\appdata\local\programs\python\python36\lib\site-packages\jupyter_core\command.py", line 134, in _jupyter_abspath
'Jupyter command `{}` not found.'.format(jupyter_subcommand)
Exception: Jupyter command `jupyter-kernelspec` not found.
However, when I run jupyter-kernelspec command on cmd it is found on PATH. Why is it happening that python is unable to locate a command if cmd can find it?

To address your specific question, you can see whether Python can locate jupyter-kernelspec (and if so, where) by running something like:
python -c "from shutil import which; print(which('jupyter-kernelspec'))"
But as to the underlying cause of the error, it seems likely that your Jupyter installation is incomplete and/or your environment is somehow misconfigured. You may want to try creating a new Python environment (perhaps using Anaconda, if you're new to Python development) and then following the QDK installation instructions again from inside that new environment (e.g., from an Anaconda command prompt with the new environment active).
Edit: From comments below, it sounds like the problem is that you have a trailing semicolon in your PATHEXT environment variable. This confuses shutil.which(), and this in turn prevents Jupyter from finding the necessary executable. (I can reproduce this problem locally by adding a trailing semicolon to PATHEXT.)
The fix should be simply to remove the trailing semicolon from PATHEXT.

Activating virtualenv from within Python script

I am trying to activate my virtualenv (already existing) using the following python code:
Test.py
import os, sys
filename = "activate"
exec(compile(open(filename, "rb").read(), filename, 'exec'), globals, locals)
print(os.system('pwd'))
if hasattr(sys, 'real_prefix'):
print('success')
else:
print('failed')
I then run this script via the terminal:
python Test.py
which then produces this error:
Traceback (most recent call last):
File "activate_this.py", line 3, in <module>
exec(compile(open(filename, "rb").read(), filename, 'exec'), globals, locals)
File "activate", line 4
deactivate () {
^
SyntaxError: invalid syntax
I can activate the virtualenv successfully by executing cd env/bin and then source activate
TLDR
Activating virtualenv from python script is throwing a syntax error from within the activate file.

The very 1st line of activate (note that VEnv is installed on Win, but this shouldn't be a problem):
# This file must be used with "source bin/activate" *from bash*
That, and the lines below should tell you that activate is a (Bourne) shell file.
[Python 3]: compile(source, filename, mode, flags=0, dont_inherit=False, optimize=-1) on the other hand, works with Python source code.
So, in order to execute the file, you'd need to use other ways, e.g. [Python 3]: subprocess - Subprocess management. You can check how I've used it: [SO]: How to effectively convert a POSIX path to Windows path with Python in Cygwin? (#CristiFati's answer).
But, I really don't see the point of doing all this, you probably misunderstood your colleague's suggestion.
Also note that even if you do manage to do it this way, all the environment variables will only be set in the calling process, so it will pretty much be unusable (well, unless you also execute your script from there too).
You should go the recommended way ([PyPA]: Virtualenv - User Guide), and that is (from bash):
source /path/to/Django/ENV/bin/activate
python your_project_startup_script.py # (as I recall, it's manage.py)

Where python keeps --prefix(sys.prefix) settings? [duplicate]

Having trouble with virtualenv on Windows 7.
I run:
virtualenv _testenv
It returns:
Traceback (most recent call last):
File "C:\Python27\Scripts\virtualenv-script.py", line 9, in <module>
load_entry_point('virtualenv==1.5.2', 'console_scripts', 'virtualenv')()
File "C:\Python27\lib\site-packages\virtualenv.py", line 558, in main
prompt=options.prompt)
File "C:\Python27\lib\site-packages\virtualenv.py", line 647, in create_environment
site_packages=site_packages, clear=clear))
File "C:\Python27\lib\site-packages\virtualenv.py", line 771, in install_python
copy_required_modules(home_dir)
File "C:\Python27\lib\site-packages\virtualenv.py", line 725, in copy_required_modules
dst_filename = change_prefix(filename, dst_prefix)
File "C:\Python27\lib\site-packages\virtualenv.py", line 710, in change_prefix
(filename, prefixes)
AssertionError: Filename c:\Python27\Lib\os.py does not start with any of these prefixes: ['C:\\Python27']
I have the following environment variables:
PYTHONHOME=C:\Python27
PYTHONPATH=c:\Python27;c:\Python27\Lib
PYTHONSTARTUP=C:\Users\Larry\.pythonrc
PATH=%PYTHONHOME%\;%PYTHONHOME%\Scripts;etc
Installed ActiveState Python:
ActivePython 2.7.2.5 (ActiveState Software Inc.) based on
Python 2.7.2 (default, Jun 24 2011, 12:21:10) [MSC v.1500 32 bit (Intel)] on win32
I updated the PYTHONPATH=C:\Python27;C:\Python27\Lib
Still looking for a solution, I found and removed AppData/Python*. Reinstalled Python and now have a different error:
C:\xbz>virtualenv _t
PYTHONHOME is set. You *must* activate the virtualenv before using it
Overwriting _t\Lib\site.py with new content
New python executable in _t\Scripts\python2.7.exe
Not overwriting existing python script _t\Scripts\python.exe (you must use _t\Scripts\python2.7.exe)
Overwriting _t\Lib\distutils\__init__.py with new content
Installing setuptools..............
Complete output from command C:\xbz\_t\Scripts\python2.7.exe -c "#!python
\"\"\"Bootstrap setuptoo...
" --always-copy -U setuptools:
Traceback (most recent call last):
File "<string>", line 278, in <module>
File "<string>", line 210, in main
File "<string>", line 132, in download_setuptools
File "C:\Python27\Lib\urllib2.py", line 94, in <module>
import httplib
File "C:\Python27\Lib\httplib.py", line 71, in <module>
import socket
File "C:\Python27\Lib\socket.py", line 47, in <module>
import _socket
ImportError: No module named _socket
----------------------------------------
...Installing setuptools...done.
Traceback (most recent call last):
File "C:\Python27\Scripts\virtualenv-script.py", line 9, in <module>
load_entry_point('virtualenv==1.5.2', 'console_scripts', 'virtualenv')()
File "C:\Python27\lib\site-packages\virtualenv.py", line 558, in main
prompt=options.prompt)
File "C:\Python27\lib\site-packages\virtualenv.py", line 654, in create_environment
install_setuptools(py_executable, unzip=unzip_setuptools)
File "C:\Python27\lib\site-packages\virtualenv.py", line 384, in install_setuptools
_install_req(py_executable, unzip)
File "C:\Python27\lib\site-packages\virtualenv.py", line 360, in _install_req
cwd=cwd)
File "C:\Python27\lib\site-packages\virtualenv.py", line 624, in call_subprocess
% (cmd_desc, proc.returncode))
OSError: Command C:\xbz\_t\Scripts\python2.7.exe -c "#!python
\"\"\"Bootstrap setuptoo...
" --always-copy -U setuptools failed with error code 1
I hacked Lib/socket.py and inserted:
import sys
sys.path = ['', 'C:\\Python27\\lib\\site-packages\\dotcloud-0.3.1-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\dotcloud.cli-0.3.1-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\flask-0.7dev_20110622-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\werkzeug-0.6.2-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\gunicorn-0.12.2-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\wtforms-0.6.3-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\repoze.browserid-0.3-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\paste-1.7.5.1-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\django_pjax-1.0-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\paramiko-1.7.7.1-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\pycrypto-2.4.1-py2.7-win32.egg', 'C:\\Python27', 'C:\\Python27\\Lib', 'C:\\Windows\\system32\\python27.zip', 'C:\\Python27\\DLLs', 'C:\\Python27\\lib\\plat-win', 'C:\\Python27\\lib\\lib-tk', 'C:\\Python27\\lib\\site-packages', 'C:\\Python27\\lib\\site-packages\\PIL', 'C:\\Python27\\lib\\site-packages\\win32', 'C:\\Python27\\lib\\site-packages\\win32\\lib', 'C:\\Python27\\lib\\site-packages\\Pythonwin', 'C:\\Python27\\lib\\site-packages\\setuptools-0.6c11-py2.7.egg-info', 'C:\\Python27\\Scripts', 'C:\\Python27\\Lib\\site-packages\\django\\bin']
Above
import _socket
The reason was that I was able to import socket from straight python prompt! So stuffed my existing path. I haven't narrowed down exactly which directory made it happy. It at least will reveal to someone else why I am getting the error without it.
Ideas? Suggestions?
Thank you. :)
I hacked Lib/socket.py and inserted:
import sys
sys.path.append('C:\\Python27\\DLLs')
Above
import _socket

3 year old question, but hopefully this answer can still help someone. Rather than setting the environment variables (which mysteriously didn't work for me), you can pass the path to your Python installation when setting up the virtual environment. In Windows, you have to path out to python.exe, but it seems that in Linux/OS X you just path to the folder. Examples:
Windows:
virtualenv -p <PATH TO PYTHON.EXE> venv
Linux/Mac:
virtualenv -p </user/path/to/python> venv
Both create a virtual environment in subfolder "venv" in current directory.

Try to set PYTHONPATH to PYTHONPATH=C:\Python27;C:\Python27\Lib (uppercase C at the start).
This can be done at the command prompt by typing set PYTHONPATH=C:\Python27;C:\Python27\Lib.
PYTHONPATH will revert back to whatever it previously was once that command prompt window is closed.

There is similar problem currently that shows error:
AssertionError: Filename C:\Python27\Lib\os.py does not start with any of
these prefixes: ['C:\\python27']
The difference is in 'C:\python27' being lower case. So the problem manifest itself in that you can not install new virtualenv or make a nested virtualenvs (we do it for testing sometimes).
The cause is in the conent of the PYTHONPATH
PYTHONPATH=C:\Python27;C:\Python27\Lib
For some reason sys.path in virtualenv.py will return c:\python27, but path to required modules will come form the PYTHONPATH and start with 'C:\Python27\Lib', hence the assertion error.
Long story short, just unset the PYTHONPATH.

For the _socket error, change your pythonpython path to:
PYTHONPATH=C:\Python27;C:\Python27\Lib;C:\Python27\DLLs

You can try the following (supppose your python is in global path):
python -m virtualenv [foldername]
This works for me, Win 10, virtualenv 15.1.0
I get it from this video, it will excute the python lib instead of calling windows exe.

I have added
if is_win:
prefixes.append('C:\PYTHON27')
to virtualenv.py and it works.

Its strange but from the error message
AssertionError: Filename c:\Python27\Lib\os.py does not start with any of these prefixes: ['C:\\Python27']
It seems, it expects the path-name for the file os.py to start with upper case 'C' and the prefix sanity check is case sensitive.
As the path to the library is derived from PYTHONPATH and in your case the drive letter is in lower case, it seems logical to change it to upper case to resolve the issue.
like
PYTHONPATH=C:\Python27;C:\Python27\Lib

I hate "summary" answers, but as I just went through a very similar issue I thought I would post my solution here as well which draws from several of these answers.
The assert error was caused because I did not have a PYTHONPATH
environment variable setup.
The socket error was caused because I did not include the
PythonXX\DLLs folder.
The full PYTHONPATH environment variable should look follows:
PYTHONPATH=C:\Python27;C:\Python27\Lib;C:\Python27\DLLs

This is an error already submitted to the Python development team: https://github.com/pypa/virtualenv/pull/697
In the meanwhile why not just change the Python installation folder name to (ptyhon27) to make the assertion work, or if you feel more confortable with that just reinstall python using the alternative location. It works with no issue.

I also ran into this problem on Windows 7. My Python27 installation was under C:\Program Files, which obviously contains a space in the path. So, on a separate Windows 7 system that did not contain Python, I did a fresh install of Python27 under C:\Python27 (the default installation path), followed by an install of setuptools (for easy_install).
Afterwards, I was able to install virtualenv CLEANLY without the above assertion error (I used easy_install).
I know that the OP's system is already using the default path, but I thought I would add my experience here as a possible solution for certain specific cases.

This issue is presumably a hangover from other more case-sensitive file systems.
Complete solution:
Read the error message from virtualenv. Remember the part where it says "does not start with any of these prefixes: ['C:\\Python27']".
Edit PYTHONPATH, or create it if you don't have one (Start+Break, Advanced system settings, Environment Variables). It shouldn't matter if it's a user variable or a system variable, unless you plan to switch user accounts.
Make the case match the error message. BOTH the drive letter AND the folder name must match (presumably intermediate folders as well, if you didn't install to C:\Python27). You can ignore the double backslash, one is fine.
The only change I made to fix the bug was as follows. The change should take effect for any new command / terminal sessions (close your open cmd.exe / powershell / etc. windows).
Old state: PYTHONPATH = C:\PYTHON27;C:\PYTHON27\LIB;C:\PYTHON27\DLLS
New state: PYTHONPATH = C:\Python27;C:\Python27\LIB;C:\Python27\DLLS
If you have any other items in your PYTHONPATH, you might as well change those too, but it probably won't affect virtualenv's ability to run.

Change "virtualenv.py" --> change_prefix with:
def change_prefix(filename, dst_prefix):
...
prefixes = sorted(prefixes, key=len, reverse=True)
filename = str(os.path.abspath(filename))[0].lower() + str(os.path.abspath(filename))[1:]
for src_prefix in prefixes:
if filename.startswith(src_prefix):
_, relpath = filename.split(src_prefix, 1)
if src_prefix != os.sep: # sys.prefix == "/"
assert relpath[0] == os.sep
relpath = relpath[1:]
return join(dst_prefix, relpath)
assert False, "Filename %s does not start with any of these prefixes: %s" % \
(filename, prefixes)
...

I had the same assertion error from a slightly different cause. The error was does not start with any of these prefixes: ['C:\\python27'] and note the lowercase "p". The actual folder names all use capital-P Python27. All the prefixes in PTYHONPATH were correct. However I had entered the PYTHONHOME variable as C:\python27 and although this was fine for Python, it caused the error in virtualenv.

Windows solution:
This is due to the difference between PYTHONPATH variable path and the one pipenv is expecting.
Suppose System Variable has below PYTHONPATH‍,
PYTHONPATH = C:\User\Bruce\AppData\Local\Programs\Python\Python37-32
And pipenv is looking for PYTHONPATH something like below:
PYTHONPATH = C:\users\bruce\appdata\local\programs\python\python37-32
Here, observe that the path text pipenv is looking has different case than what is set in System Environment variable.
To solve this issue try below steps by opening command prompt in folder where pipenv is to run:
> set PYTHONPATH=C:\users\bruce\appdata\local\programs\python\python37-32
You need to give exact same path that is shown in the AssertionError.
Then run below command to create pipenv
> pipenv install numpy
Any other library can be installed

virtualenv on windows 7 returns AssertionError

Having trouble with virtualenv on Windows 7.
I run:
virtualenv _testenv
It returns:
Traceback (most recent call last):
File "C:\Python27\Scripts\virtualenv-script.py", line 9, in <module>
load_entry_point('virtualenv==1.5.2', 'console_scripts', 'virtualenv')()
File "C:\Python27\lib\site-packages\virtualenv.py", line 558, in main
prompt=options.prompt)
File "C:\Python27\lib\site-packages\virtualenv.py", line 647, in create_environment
site_packages=site_packages, clear=clear))
File "C:\Python27\lib\site-packages\virtualenv.py", line 771, in install_python
copy_required_modules(home_dir)
File "C:\Python27\lib\site-packages\virtualenv.py", line 725, in copy_required_modules
dst_filename = change_prefix(filename, dst_prefix)
File "C:\Python27\lib\site-packages\virtualenv.py", line 710, in change_prefix
(filename, prefixes)
AssertionError: Filename c:\Python27\Lib\os.py does not start with any of these prefixes: ['C:\\Python27']
I have the following environment variables:
PYTHONHOME=C:\Python27
PYTHONPATH=c:\Python27;c:\Python27\Lib
PYTHONSTARTUP=C:\Users\Larry\.pythonrc
PATH=%PYTHONHOME%\;%PYTHONHOME%\Scripts;etc
Installed ActiveState Python:
ActivePython 2.7.2.5 (ActiveState Software Inc.) based on
Python 2.7.2 (default, Jun 24 2011, 12:21:10) [MSC v.1500 32 bit (Intel)] on win32
I updated the PYTHONPATH=C:\Python27;C:\Python27\Lib
Still looking for a solution, I found and removed AppData/Python*. Reinstalled Python and now have a different error:
C:\xbz>virtualenv _t
PYTHONHOME is set. You *must* activate the virtualenv before using it
Overwriting _t\Lib\site.py with new content
New python executable in _t\Scripts\python2.7.exe
Not overwriting existing python script _t\Scripts\python.exe (you must use _t\Scripts\python2.7.exe)
Overwriting _t\Lib\distutils\__init__.py with new content
Installing setuptools..............
Complete output from command C:\xbz\_t\Scripts\python2.7.exe -c "#!python
\"\"\"Bootstrap setuptoo...
" --always-copy -U setuptools:
Traceback (most recent call last):
File "<string>", line 278, in <module>
File "<string>", line 210, in main
File "<string>", line 132, in download_setuptools
File "C:\Python27\Lib\urllib2.py", line 94, in <module>
import httplib
File "C:\Python27\Lib\httplib.py", line 71, in <module>
import socket
File "C:\Python27\Lib\socket.py", line 47, in <module>
import _socket
ImportError: No module named _socket
----------------------------------------
...Installing setuptools...done.
Traceback (most recent call last):
File "C:\Python27\Scripts\virtualenv-script.py", line 9, in <module>
load_entry_point('virtualenv==1.5.2', 'console_scripts', 'virtualenv')()
File "C:\Python27\lib\site-packages\virtualenv.py", line 558, in main
prompt=options.prompt)
File "C:\Python27\lib\site-packages\virtualenv.py", line 654, in create_environment
install_setuptools(py_executable, unzip=unzip_setuptools)
File "C:\Python27\lib\site-packages\virtualenv.py", line 384, in install_setuptools
_install_req(py_executable, unzip)
File "C:\Python27\lib\site-packages\virtualenv.py", line 360, in _install_req
cwd=cwd)
File "C:\Python27\lib\site-packages\virtualenv.py", line 624, in call_subprocess
% (cmd_desc, proc.returncode))
OSError: Command C:\xbz\_t\Scripts\python2.7.exe -c "#!python
\"\"\"Bootstrap setuptoo...
" --always-copy -U setuptools failed with error code 1
I hacked Lib/socket.py and inserted:
import sys
sys.path = ['', 'C:\\Python27\\lib\\site-packages\\dotcloud-0.3.1-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\dotcloud.cli-0.3.1-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\flask-0.7dev_20110622-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\werkzeug-0.6.2-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\gunicorn-0.12.2-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\wtforms-0.6.3-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\repoze.browserid-0.3-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\paste-1.7.5.1-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\django_pjax-1.0-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\paramiko-1.7.7.1-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\pycrypto-2.4.1-py2.7-win32.egg', 'C:\\Python27', 'C:\\Python27\\Lib', 'C:\\Windows\\system32\\python27.zip', 'C:\\Python27\\DLLs', 'C:\\Python27\\lib\\plat-win', 'C:\\Python27\\lib\\lib-tk', 'C:\\Python27\\lib\\site-packages', 'C:\\Python27\\lib\\site-packages\\PIL', 'C:\\Python27\\lib\\site-packages\\win32', 'C:\\Python27\\lib\\site-packages\\win32\\lib', 'C:\\Python27\\lib\\site-packages\\Pythonwin', 'C:\\Python27\\lib\\site-packages\\setuptools-0.6c11-py2.7.egg-info', 'C:\\Python27\\Scripts', 'C:\\Python27\\Lib\\site-packages\\django\\bin']
Above
import _socket
The reason was that I was able to import socket from straight python prompt! So stuffed my existing path. I haven't narrowed down exactly which directory made it happy. It at least will reveal to someone else why I am getting the error without it.
Ideas? Suggestions?
Thank you. :)
I hacked Lib/socket.py and inserted:
import sys
sys.path.append('C:\\Python27\\DLLs')
Above
import _socket

3 year old question, but hopefully this answer can still help someone. Rather than setting the environment variables (which mysteriously didn't work for me), you can pass the path to your Python installation when setting up the virtual environment. In Windows, you have to path out to python.exe, but it seems that in Linux/OS X you just path to the folder. Examples:
Windows:
virtualenv -p <PATH TO PYTHON.EXE> venv
Linux/Mac:
virtualenv -p </user/path/to/python> venv
Both create a virtual environment in subfolder "venv" in current directory.

Try to set PYTHONPATH to PYTHONPATH=C:\Python27;C:\Python27\Lib (uppercase C at the start).
This can be done at the command prompt by typing set PYTHONPATH=C:\Python27;C:\Python27\Lib.
PYTHONPATH will revert back to whatever it previously was once that command prompt window is closed.

There is similar problem currently that shows error:
AssertionError: Filename C:\Python27\Lib\os.py does not start with any of
these prefixes: ['C:\\python27']
The difference is in 'C:\python27' being lower case. So the problem manifest itself in that you can not install new virtualenv or make a nested virtualenvs (we do it for testing sometimes).
The cause is in the conent of the PYTHONPATH
PYTHONPATH=C:\Python27;C:\Python27\Lib
For some reason sys.path in virtualenv.py will return c:\python27, but path to required modules will come form the PYTHONPATH and start with 'C:\Python27\Lib', hence the assertion error.
Long story short, just unset the PYTHONPATH.

For the _socket error, change your pythonpython path to:
PYTHONPATH=C:\Python27;C:\Python27\Lib;C:\Python27\DLLs

You can try the following (supppose your python is in global path):
python -m virtualenv [foldername]
This works for me, Win 10, virtualenv 15.1.0
I get it from this video, it will excute the python lib instead of calling windows exe.

I have added
if is_win:
prefixes.append('C:\PYTHON27')
to virtualenv.py and it works.

Its strange but from the error message
AssertionError: Filename c:\Python27\Lib\os.py does not start with any of these prefixes: ['C:\\Python27']
It seems, it expects the path-name for the file os.py to start with upper case 'C' and the prefix sanity check is case sensitive.
As the path to the library is derived from PYTHONPATH and in your case the drive letter is in lower case, it seems logical to change it to upper case to resolve the issue.
like
PYTHONPATH=C:\Python27;C:\Python27\Lib

I hate "summary" answers, but as I just went through a very similar issue I thought I would post my solution here as well which draws from several of these answers.
The assert error was caused because I did not have a PYTHONPATH
environment variable setup.
The socket error was caused because I did not include the
PythonXX\DLLs folder.
The full PYTHONPATH environment variable should look follows:
PYTHONPATH=C:\Python27;C:\Python27\Lib;C:\Python27\DLLs

This is an error already submitted to the Python development team: https://github.com/pypa/virtualenv/pull/697
In the meanwhile why not just change the Python installation folder name to (ptyhon27) to make the assertion work, or if you feel more confortable with that just reinstall python using the alternative location. It works with no issue.

I also ran into this problem on Windows 7. My Python27 installation was under C:\Program Files, which obviously contains a space in the path. So, on a separate Windows 7 system that did not contain Python, I did a fresh install of Python27 under C:\Python27 (the default installation path), followed by an install of setuptools (for easy_install).
Afterwards, I was able to install virtualenv CLEANLY without the above assertion error (I used easy_install).
I know that the OP's system is already using the default path, but I thought I would add my experience here as a possible solution for certain specific cases.

This issue is presumably a hangover from other more case-sensitive file systems.
Complete solution:
Read the error message from virtualenv. Remember the part where it says "does not start with any of these prefixes: ['C:\\Python27']".
Edit PYTHONPATH, or create it if you don't have one (Start+Break, Advanced system settings, Environment Variables). It shouldn't matter if it's a user variable or a system variable, unless you plan to switch user accounts.
Make the case match the error message. BOTH the drive letter AND the folder name must match (presumably intermediate folders as well, if you didn't install to C:\Python27). You can ignore the double backslash, one is fine.
The only change I made to fix the bug was as follows. The change should take effect for any new command / terminal sessions (close your open cmd.exe / powershell / etc. windows).
Old state: PYTHONPATH = C:\PYTHON27;C:\PYTHON27\LIB;C:\PYTHON27\DLLS
New state: PYTHONPATH = C:\Python27;C:\Python27\LIB;C:\Python27\DLLS
If you have any other items in your PYTHONPATH, you might as well change those too, but it probably won't affect virtualenv's ability to run.

Change "virtualenv.py" --> change_prefix with:
def change_prefix(filename, dst_prefix):
...
prefixes = sorted(prefixes, key=len, reverse=True)
filename = str(os.path.abspath(filename))[0].lower() + str(os.path.abspath(filename))[1:]
for src_prefix in prefixes:
if filename.startswith(src_prefix):
_, relpath = filename.split(src_prefix, 1)
if src_prefix != os.sep: # sys.prefix == "/"
assert relpath[0] == os.sep
relpath = relpath[1:]
return join(dst_prefix, relpath)
assert False, "Filename %s does not start with any of these prefixes: %s" % \
(filename, prefixes)
...

I had the same assertion error from a slightly different cause. The error was does not start with any of these prefixes: ['C:\\python27'] and note the lowercase "p". The actual folder names all use capital-P Python27. All the prefixes in PTYHONPATH were correct. However I had entered the PYTHONHOME variable as C:\python27 and although this was fine for Python, it caused the error in virtualenv.

Windows solution:
This is due to the difference between PYTHONPATH variable path and the one pipenv is expecting.
Suppose System Variable has below PYTHONPATH‍,
PYTHONPATH = C:\User\Bruce\AppData\Local\Programs\Python\Python37-32
And pipenv is looking for PYTHONPATH something like below:
PYTHONPATH = C:\users\bruce\appdata\local\programs\python\python37-32
Here, observe that the path text pipenv is looking has different case than what is set in System Environment variable.
To solve this issue try below steps by opening command prompt in folder where pipenv is to run:
> set PYTHONPATH=C:\users\bruce\appdata\local\programs\python\python37-32
You need to give exact same path that is shown in the AssertionError.
Then run below command to create pipenv
> pipenv install numpy
Any other library can be installed

Categories

Resources