On Mar 28, 6:05 pm, Dwayne Blind <[email protected]> wrote: > Thanks Josh. I reply late because I went on holidays. > > Python is installed in the C:\Python27\ directory. So I saved the go- > pylons.py file into that directory. > > Then in the cmd, I typed : C:\Python27>python.exe go-pylons.py --no- > site-packages mydevenv > Is this correct ?
The idea behind virtualenv (which go-pylons.py is based on) is to set up a Python environment that's separate from the system Python installation. (This has a couple of benefits: it means that you run no risk of breaking the system Python installation, and it makes it possible to run different Python programs with different library requirements on the same system, by having them run out of different environments.) Since you're specifying a directory of mydevenv with a current directory of c:\python27, you're making your environment a subdirectory of your system Python installation. That's probably not recommended (although I don't think it's causing the particular problem you're seeing). Try c:\mydevenv (if it's a single user system) or c:\Users\dwayne\devenv instead. I've used Pylons in Windows Vista and Python 2.7 without any problems, so I'm not sure why it's not working. You might try adding the -v option to go-pylons.py (verbose, for extra logging) and posting the results here. I did notice that the installation procedure I followed was a bit different: 1) I downloaded setuptools from http://pypi.python.org/pypi/setuptools. 2) I used setuptools's easy_install to install virtualenv to my system Python installation: easy_install virtualenv 3) I ran go-pylons.py (using the same procedure you did). I think that at this point go-pylons.py is using my newer, system-installed virtualenv instead of its bundled version. This may make a difference. I haven't used Django, so I can't compare. From what you've described, it seems like what you're running into is simply the learning curve associated with doing any Python development in Windows, rather than issues specific to Pylons. It shouldn't take too much more work to get things working, but if you really want to avoid that learning curve, you could always give Linux a try; Linux generally provides better built-in support for programming tools, and documentation for working with open source programming on Linux is often a bit better. You can try andLinux (which I haven't used) to run Linux software in Windows, or you can use VirtualBox to run an Ubuntu VM from within your Windows OS, or you can install Ubuntu alongside Windows (if you have the disk space to spare and don't mind rebooting to switch OSes). Hope this helps. -- Josh Kelley -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
