Re: [Visualpython-users] Vpython installation defaults to C:\VPython

[Bruce S. <ba...@an...>]

--On Tuesday, January 16, 2001 3:00 PM +0800 LUK ShunTim 
<ce...@po...> wrote:

> It appears that the self-installing Win32 version VPython-2001-01-15.exe
> installes to C:\VPython by deafult. (It did nod ask for ainstead of to
> my python directory which is at e:\py. Is this the default behaviour of
> have I missed something?
> I'm using the ActivePython distribution from ActiveState.
>
> While the files can be moved manually, maybe it can (also) be
> distributed as a zipped archive so that it can be unzipped under the
> appropriate python root.

Thank you for the report. I have added the following comment on the Windows 
download page:

(If you installed a version of Python 2.0 other than the one listed above, 
the VPython installer may install files into a folder on the system drive 
named "VPython". Move these files into your Python folder. The reason for 
this behavior is explained in the FAQ section.)

I have also added the following note to the FAQ:

When we gave such a choice in the past, we found that novice users 
frequently installed Python into an odd location and then installed the 
VPython components into a different folder, so that VPython wouldn't run. 
Now, if the novice installs the standard Python 2.0, the VPython installer 
automatically determines the Python folder location by reading information 
in the Windows registry. This is a much safer scheme for the novice. If you 
have installed some other version of Python 2.0, the VPython installer may 
not be able to find Python and will then install into a "VPython" folder on 
the system drive (typically C:\). After installing, simply move the files 
in that folder into the Python folder.

---------------------------------
Additional comment: It is advantageous to have Visual (VPython) separate 
from Python itself. But when we tried to have novices add VPython using a 
zip file, mistakes were very frequent. There is a conflict between making 
installation fool-proof for most novices and especially convenient for 
experts (and/or a minority of users who have installed some other flavor of 
Python). We consider the former goal more important than the latter.

With the installer I'm using (Inno Setup), there doesn't seem to be a way 
to detect that Python couldn't be found and then (only) in that case ask 
for the Python folder. But I'm certainly open to suggestions for 
improvements.

Bruce Sherwood