Proper set-up for a co-existant python 2.6 & 3.1 installation

[vsoler]

*** Posted previously in Windows 7 forum but no answer ***

I have installed two different versions of a scripting language called
Python in my Windows 7 PC.

Even though I have not fully tested them, they seem to work if I
launch them from the proper directory:

CUsers\python26 for python 2.6
CUsers\pythom31 for python 3.1

In either case, I have use the default installation procedure.

In both cases the executable is python.exe
In both cases the *.py file should launch the respective python.exe
executable

Both versions are slightly incompatible (that is, completely
incompatible)

I keep the *.py for python 2.6 in one directory, the *.py for python
3.1 in another directory.

I would like to set-up my PC so that I can easily run either version
of python without having to uninstall one version and its associated
libraries, and without having to install the other version and its
associated libraries.

I would like something easy.

I have thought of creating two .BAT files, for changing the file
associations back and forth.

However, I have read somewhere that changes made in a CMD.exe window
are not permament, and its effects are cancelled as soon as the CMD
window is closed.

So I try to change the files that my PC reads when it boots. But here
I get lost, since I do not know what to change, where to change it,
and how to make changes back and forth in an easy way.

I think that somebody might come up with an idea or suggestion that
would help me solve my problem.

Any help is highly appreciated.

Vicente Soler

 

[Michael]

"vsoler" <vicente.soler@gmail.com> wrote in message
news:6eddc01d-19c3-481d-b5b7-8bf9e3d453c6@t2g2000yqe.googlegroups.com...
> *** Posted previously in Windows 7 forum but no answer ***

....and your XP question is, for the second time?

--

"Don't pick a fight with an old man.
If he is too old to fight, he'll just kill you."

 

[Ben Dover]

So, why are you posting it in a Windows XP newsgroup, Hooplehead? Perhaps it
would be just as appropriate to ask it in a General Motoros forum.

"vsoler" <vicente.soler@gmail.com> wrote in message
news:6eddc01d-19c3-481d-b5b7-8bf9e3d453c6@t2g2000yqe.googlegroups.com...
> *** Posted previously in Windows 7 forum but no answer ***
>
> I have installed two different versions of a scripting language called
> Python in my Windows 7 PC.
>
> Even though I have not fully tested them, they seem to work if I
> launch them from the proper directory:
>
> CUsers\python26 for python 2.6
> CUsers\pythom31 for python 3.1
>
> In either case, I have use the default installation procedure.
>
> In both cases the executable is python.exe
> In both cases the *.py file should launch the respective python.exe
> executable
>
> Both versions are slightly incompatible (that is, completely
> incompatible)
>
> I keep the *.py for python 2.6 in one directory, the *.py for python
> 3.1 in another directory.
>
> I would like to set-up my PC so that I can easily run either version
> of python without having to uninstall one version and its associated
> libraries, and without having to install the other version and its
> associated libraries.
>
> I would like something easy.
>
> I have thought of creating two .BAT files, for changing the file
> associations back and forth.
>
> However, I have read somewhere that changes made in a CMD.exe window
> are not permament, and its effects are cancelled as soon as the CMD
> window is closed.
>
> So I try to change the files that my PC reads when it boots. But here
> I get lost, since I do not know what to change, where to change it,
> and how to make changes back and forth in an easy way.
>
> I think that somebody might come up with an idea or suggestion that
> would help me solve my problem.
>
> Any help is highly appreciated.
>
> Vicente Soler