• Welcome to Tux Reports: Where Penguins Fly. We hope you find the topics varied, interesting, and worthy of your time. Please become a member and join in the discussions.

Permanent file association *** install 2 versions of same package

V

vsoler

Flightless Bird
*** 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:

C:/Users\python26 for python 2.6
C:/Users\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
 
M

Michael

Flightless Bird
"vsoler" <vicente.soler@gmail.com> wrote in message
news:19f8696e-5eb6-4ed4-950a-40554b7ea394@x42g2000yqx.googlegroups.com...
> *** posted previously in Windows 7 forum, but no answer ***


....and your XP question is?

--

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

vsoler

Flightless Bird
On 24 ago, 19:05, "Michael" <ds...@sdhfsd.com> wrote:
> "vsoler" <vicente.so...@gmail.com> wrote in message
>
> news:19f8696e-5eb6-4ed4-950a-40554b7ea394@x42g2000yqx.googlegroups.com...
>
> > *** posted previously in Windows 7 forum, but no answer ***

>
> ...and your XP question is?
>
> --
>
> "Don't pick a fight with an old man.
> If he is too old to fight, he'll just kill you."


I think that the problem that I have has the same solution in all
Windows starting in Windows XP. This is why I posted here.

However, strictly speaking, I have a Windows 7 system.
 
U

Unknown

Flightless Bird
I doubt anyone knows what you're talking about. Do you have a problem?
What is it?
"vsoler" <vicente.soler@gmail.com> wrote in message
news:d8bcbcfb-5e9f-45bc-b7de-33e24227f3fd@l20g2000yqm.googlegroups.com...
> On 24 ago, 19:05, "Michael" <ds...@sdhfsd.com> wrote:
>> "vsoler" <vicente.so...@gmail.com> wrote in message
>>
>> news:19f8696e-5eb6-4ed4-950a-40554b7ea394@x42g2000yqx.googlegroups.com...
>>
>> > *** posted previously in Windows 7 forum, but no answer ***

>>
>> ...and your XP question is?
>>
>> --
>>
>> "Don't pick a fight with an old man.
>> If he is too old to fight, he'll just kill you."

>
> I think that the problem that I have has the same solution in all
> Windows starting in Windows XP. This is why I posted here.
>
> However, strictly speaking, I have a Windows 7 system.
 
B

Bob I

Flightless Bird
r-click, Open With, pick.

vsoler wrote:
> On 24 ago, 19:05, "Michael" <ds...@sdhfsd.com> wrote:
>
>>"vsoler" <vicente.so...@gmail.com> wrote in message
>>
>>news:19f8696e-5eb6-4ed4-950a-40554b7ea394@x42g2000yqx.googlegroups.com...
>>
>>
>>>*** posted previously in Windows 7 forum, but no answer ***

>>
>>...and your XP question is?
>>
>>--
>>
>>"Don't pick a fight with an old man.
>>If he is too old to fight, he'll just kill you."

>
>
> I think that the problem that I have has the same solution in all
> Windows starting in Windows XP. This is why I posted here.
>
> However, strictly speaking, I have a Windows 7 system.
 
T

Tim Meddick

Flightless Bird
Use the : "Control Panel" - "Folder Options" - "File Types" (tab)

....and scroll down to "*.py " files, click on the "Advanced" button and
then on the "Edit" button to edit the available commands that will show up
on the file-type's right-click menu.

The command named "open" is the one that normally opens the file-type when
you double-click on the file, without going through the right-click menu.
But you can change the default here as well by selecting or adding an other
command and clicking on the "set default" button.

You could use this "File Types" feature to create a right-click menu with
two commands so you can choose which version of the program to open a file
of this type.

Or, just check and edit the existing "open" command, to make sure it's
always going to be the right version that always opens files of this type.


==

Cheers, Tim Meddick, Peckham, London. :)




"vsoler" <vicente.soler@gmail.com> wrote in message
news:19f8696e-5eb6-4ed4-950a-40554b7ea394@x42g2000yqx.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:
>
> C:/Users\python26 for python 2.6
> C:/Users\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
 
Top