On 26/07/2013 10:25 PM, D. Xenakis wrote:
Apparently my problem was that i did not have correctly setup the new path..
But hey - learning is a good thing
+1!
Also, good job on posting the solution you found as well, that's always
helpful if anyone else hits the same problem.
Personally, I t
Yeah trying to run virtualenv under IDLE was a desperate move as i couldnt make
anything work under cmd.
Apparently my problem was that i did not have correctly setup the new path..
Solution for me was the following from
"http://forums.udacity.com/questions/100064678/pip-installation-instructi
On 25/07/2013 11:48 PM, D. Xenakis wrote:
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..
virtualenv is intended to be a command line tool, so running it through
idle is
Got similar things. Don't know what is the root cause but enabling
distribute seems to work...
c:\_work\home>virtualenv --distribute pyve\openpyxl
New python executable in pyve\openpyxl\Scripts\python.exe
A globally installed setuptools was found (in c:\python25\lib\site-
packages)
Use the --no-si