[Grok-dev] How you can help improving Windows support

Roger Erens roger.erens at e-s-c.biz
Tue Apr 14 16:47:51 EDT 2009

on 14-4-2009 18:00 Milind Khadilkar wrote:
> Hi Roger,
> My responses inline in (* *) below:
> Thanks.
> Milind

>     III) when you create a virtual environment with the
>     --no-site-packages option, I would expect an error about a missing
>     win32api module or some such. What happens when you invoke python
>     after having activated your virtual environment in step 7) and try
>     to import win32api?
>     (*I do not get any error if I install grokproject with the
>     --no-site-packages option, except that the server bombs after
>     starting up. However, if I install grokproject without the switch, I
>     get the error Import Error: No module named schemaless. Thre has
>     been no explicit error related to win32api since 1.0a3 *)

I don't understand this.
>     IV) after activating your virtual environment in step 7), issue the
>     command:
>     echo %PATH%
>     You ought to find something like E:\vgrok\\Scripts in the output
>     from that command, meaning that easy_install and grokproject will be
>     found without prefixing them with \Scripts. If %PATH% does not
>     contain that directory _and_ you forgot to prefix the commands with
>     \Scripts, you may have used the system's easy_install and
>     grokproject commands; you then have a lot of cleaning up to do
>     before retrying another installation procedure!
> (* My mistake: in one of the trials I had not activated the virtual 
> environment. In any case, I have always been using Scripts\ explicitly. 
> Incidentally, after activating, the Path environment also contains 
> C:\python24. Is it alright?*)

It will do so also before activating, since this folder is added to 
%PATH% by the Python2.4-installer

> (** Note:   Apart from Script not being available in path, I have not 
> found any difference in behaviour whether I explicitly activate the 
> virtual environment or not **)

How about starting up Python in both situations and:

import sys
print sys.path



More information about the Grok-dev mailing list