Python-2.2a1.exe: "Can't run 16-bit Windows program"

[John Schmitt]

> -----Original Message-----
> From: Tim Peters [mailto:tim.one at home.com]
> Sent: Friday, August 10, 2001 1:32 PM
> To: python-list at python.org
> Subject: RE: Python-2.2a1.exe: "Can't run 16-bit Windows program"
> 
> 
> [John Schmitt]
> > I am an admin on this machine.
> 
> If you're an Admin but don't know why your box can't run a 
> 16-bit program,
> you probably shouldn't be an Admin <wink>.  This shouldn't be 

Ah.  I think I'm with ya.  <wink>

> happening in
> "a normal" Win2K setup.
> 
> > ...
> > Is there a way of switching back and forth between 2.1 and 2.2?
> 
> Sorry, I don't know what you're asking.  If you install them 

No need to be sorry.  Indeed, *I'm* sorry.  What I meant was, if I have a
Python program in my %PATH% somewhere, say

c:\bin\foo.py

and I'm launch that program from the command prompt like this:

d:\myproject\skunkworks\> foo

(I have %PATHEXT% set correctly)

I'd like to be able to set a switch somewhere that decides whether to use
ActiveState 2.1, python.org 2.2a1, 2.2a2, etc.  Since you have several
Python installations going at the same time, perhaps you can share how you
manage all these installations.

> into different
> directories, what else do you think *might* be needed?  

Um, %PYTHONHOME%, %PYTHONPATH% etc might need adjusting.

[...my painful installer babble omitted...]

John

Thanks for your help.

BTW, is your <wink> emoticon overloaded?  I'm not completely confident that
I grok what it is meant to convey.  Can you help me out with that too?