How come Pylons is not recognized when I run 'import pylons' in Windows Vista command prompt?

When I try to import pylons in the virtual python environment I get the error

C:\env\Scripts>python
Python 2.7 (r27:82525, Jul  4 2010, 07:43:08) [MSC v.1500 64 bit (A
MD64)] on win32
Type "help", "copyright", "credits" or "license" for more informati
on.
>>> import pylons
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\env\lib\site-packages\pylons-1.0-py2.7.egg\pylons\__init
__.py", line 6, in <module>
    from paste.registry import StackedObjectProxy
ImportError: No module named registry

As I understand this error, Python is telling me that it can not find the module named registry. Perhaps this is a result of the error I got while installing Pylons which is explained over here Why do I get an error on the last line of install开发者_开发技巧ing Pylons 1.0 with easy_install and Python 2.7 in Windows Vista 64?

It seems that many of the Pylon components were installed but I guess registry was not or maybe Pylons just can not see it.

Any ideas on how to solve this?

You have to activate the virtual environment before you can import pylons.

C:\Users\Josh>env\scripts\activate
(env) C:\Users\Josh>python
ActivePython 2.6.2.2 (ActiveState Software Inc.) based on
Python 2.6.2 (r262:71600, Apr 21 2009, 15:05:37) [MSC v.1500 32 bit (Intel)] on
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import pylons
>>>

vs. this

C:\Users\Josh\env\Scripts>python
ActivePython 2.6.2.2 (ActiveState Software Inc.) based on
Python 2.6.2 (r262:71600, Apr 21 2009, 15:05:37) [MSC v.1500 32 bit (Intel)] on
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> pylons
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'pylons' is not defined
>>>

I guessing that you have the pylons package installed outside and inside your virtual environment. So python is letting you import pylons but the paste package is not installed outside of your virtual environment so you are getting an error.

Running the activate batch script (should be inside your env\Scripts folder) should solve the problem.