Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #33709

windows question: default click action points to wrong python version

From Gelonida N <gelonida@gmail.com>
Subject windows question: default click action points to wrong python version
Date 2012-11-21 09:23 +0100
Newsgroups comp.lang.python
Message-ID <mailman.133.1353486194.29569.python-list@python.org> (permalink)

Show all headers | View raw


Hi,

I installed python 2.6 and python 2.7 on a windows 7 machine.

At the moment Python 2.7 is the interpreter being used if I 'start' a 
python script without explicit interpreter.

I always thought, that 'repairing' Python 2.6 (reinstalling it) would 
set the default settings back to Python 2.6.

I also see with assoc / ftypes, that python 2.6. has now been configured 
as default.

However when I click on a script it is still started with 2.7.
(even after a full restart of the machine)

This is really surprising to me.
I thought ftype is the command to change file associations.

What am I missing?

Back to comp.lang.python | Previous | NextNext in thread | Find similar | Unroll thread


Thread

windows question: default click action points to wrong python version Gelonida N <gelonida@gmail.com> - 2012-11-21 09:23 +0100
  Re: windows question: default click action points to wrong python version Tony the Tiger <tony@tiger.invalid> - 2012-11-21 14:53 -0600
    Re: windows question: default click action points to wrong python version Tim Golden <mail@timgolden.me.uk> - 2012-11-21 21:14 +0000

csiph-web