Thanks, Uli.<br><br>I have only one installation of python. <br><br>The path to _socket in my python installation matches yours:<br>>>> import _socket<br>>>> _socket.__file__<br>'c:\\python25\\DLLs\\_socket.pyd'<br>
<br>In the virtual environment, sys.path is:<br>(vgrok) C:\vgrok>python<br>Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit (Intel)] on<br>win32<br>Type "help", "copyright", "credits" or "license" for more information.<br>
>>> import sys<br>>>> sys.path<br>['', 'C:\\vgrok\\lib\\site-packages\\setuptools-0.6c9-py2.5.egg', 'c:\\python25\<br>\lib', 'C:\\WINDOWS\\system32\\python25.zip', 'C:\\vgrok\\DLLs', 'C:\\vgrok\\lib<br>
', 'C:\\vgrok\\lib\\plat-win', 'C:\\vgrok\\lib\\lib-tk', 'C:\\vgrok\\Scripts', '<br>C:\\vgrok', 'C:\\vgrok\\lib\\site-packages']<br>>>><br><br>There is no _socket in the DLLs folder of the virtual environment; the \Python25\DLLs is not in the path of the virtual environment.<br>
<br>I am currently using grok installed directly on my "real" python environment.<br><br>Thanks and Regards<br><br><br>Milind<br><div class="gmail_quote">On Mon, Sep 7, 2009 at 4:47 PM, Uli Fouquet <span dir="ltr"><<a href="mailto:uli@gnufix.de">uli@gnufix.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Milind,<br>
<div class="im"><br>
Milind Khadilkar wrote:<br>
<br>
> I successfully (but reluctantly) installed grokproject on the<br>
> installed python (i.e. without the virtual environment). I wonder what<br>
> will break with my other python/zope applications.<br>
<br>
</div>Hm, difficult to guess. From my limited experience Grok (and Zope in<br>
general) won't block other Python code, but the other way round could be<br>
a problem. So, if it works without virtualenv for you I'd say you can go<br>
with it.<br>
<div class="im"><br>
> The Python I am using is the MS Windows installable version 2.5.4<br>
<br>
</div>Using the MSI? Okay, I have the same version running here.<br>
<br>
Milind, it would really be helpful if you could post the output of the<br>
following commands. No one can help you, if we do not know the paths<br>
etc.<br>
<br>
Most probably there is a DLL missing, but only in your virtualenv, which<br>
is strange. If there are any other Python versions installed on your<br>
system: are you sure, you created the virtualenv for the freshly<br>
installed Python2.5 (you can use virtualenvs '-p' option for this)?<br>
<br>
Then: what is the path to your working _socket module? In my install it<br>
is:<br>
<br>
C:\> Python25\python.exe<br>
>>> import _socket<br>
>>> _socket.__file__<br>
'C:\\Python25\\DLLs\\_socket.pyd'<br>
<br>
When you activate your virtualenv, what does sys.path give? Here it<br>
looks like this:<br>
<br>
C:\> sandbox_clean25\scripts\activate.bat<br>
(SANDBO~2) C:\> python<br>
>>> import sys<br>
>>> sys.path<br>
[..., 'C:\\Python25\\DLLs', ...]<br>
<br>
Best regards,<br>
<br>
--<br>
<font color="#888888">Uli<br>
<br>
</font></blockquote></div><br>