[Grok-dev] Cannot easyinstall grokproject

[Milind Khadilkar]

Thanks, Uli.

I have only one installation of python.

The path to _socket in my python installation matches yours:
>>> import _socket
>>> _socket.__file__
'c:\\python25\\DLLs\\_socket.pyd'

In the virtual environment, sys.path is:
(vgrok) C:\vgrok>python
Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit (Intel)]
on
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path
['', 'C:\\vgrok\\lib\\site-packages\\setuptools-0.6c9-py2.5.egg',
'c:\\python25\
\lib', 'C:\\WINDOWS\\system32\\python25.zip', 'C:\\vgrok\\DLLs',
'C:\\vgrok\\lib
', 'C:\\vgrok\\lib\\plat-win', 'C:\\vgrok\\lib\\lib-tk',
'C:\\vgrok\\Scripts', '
C:\\vgrok', 'C:\\vgrok\\lib\\site-packages']
>>>

There is no _socket in the DLLs folder of the virtual environment; the
\Python25\DLLs is not in the path of the virtual environment.

I am currently using grok installed directly on my "real" python
environment.

Thanks and Regards


Milind
On Mon, Sep 7, 2009 at 4:47 PM, Uli Fouquet <uli at gnufix.de> wrote:

> Hi Milind,
>
> Milind Khadilkar wrote:
>
> > I successfully (but reluctantly) installed grokproject on the
> > installed python (i.e. without the virtual environment). I wonder what
> > will break with my other python/zope applications.
>
> Hm, difficult to guess. From my limited experience Grok (and Zope in
> general) won't block other Python code, but the other way round could be
> a problem. So, if it works without virtualenv for you I'd say you can go
> with it.
>
> > The Python I am using is the MS Windows installable version 2.5.4
>
> Using the MSI? Okay, I have the same version running here.
>
> Milind, it would really be helpful if you could post the output of the
> following commands. No one can help you, if we do not know the paths
> etc.
>
> Most probably there is a DLL missing, but only in your virtualenv, which
> is strange. If there are any other Python versions installed on your
> system: are you sure, you created the virtualenv for the freshly
> installed Python2.5 (you can use virtualenvs '-p' option for this)?
>
> Then: what is the path to your working _socket module? In my install it
> is:
>
>  C:\> Python25\python.exe
>  >>> import _socket
>  >>> _socket.__file__
>  'C:\\Python25\\DLLs\\_socket.pyd'
>
> When you activate your virtualenv, what does sys.path give? Here it
> looks like this:
>
>   C:\> sandbox_clean25\scripts\activate.bat
>   (SANDBO~2) C:\> python
>   >>> import sys
>   >>> sys.path
>   [..., 'C:\\Python25\\DLLs', ...]
>
> Best regards,
>
> --
> Uli
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.zope.org/pipermail/grok-dev/attachments/20090910/e737a3fd/attachment.html