Ask Your Question

Revision history [back]

Link *.py files to wing-personal.exe

In Windows 7, I'd like to have the IDE start up as soon as I double click on a *.py file.While this worked well in previous versions, this is no longer the case for 6.0.7.-1 personal.What happens now is that the *.py file gets directly executed when I use wing-personal.exe as the standard app for execution.Using console_wing-personal.exe instead works, but shows an additional nasty console window I'd rather try to avoid.What am I missing?

Link *.py files to wing-personal.exe

In Windows 7, I'd like to have the IDE start up as soon as I double click on a *.py file.While file.

While this worked well in previous versions, this is no longer the case for 6.0.7.-1 personal.What personal.

What happens now is that the *.py file gets directly executed when I use wing-personal.exe as the standard app for execution.Using execution.

Using console_wing-personal.exe instead works, but shows an additional nasty console window I'd rather try to avoid.What avoid.

What am I missing?

Link *.py files to wing-personal.exe

In Windows 7, I'd like to have the IDE start up as soon as I double click on a *.py file.

While this worked well in previous versions, this is no longer the case for 6.0.7.-1 personal.

What happens now is that the *.py file gets directly executed when I use wing-personal.exe as the standard app for execution.

Using console_wing-personal.exe instead works, but shows an additional nasty console window I'd rather try to avoid.

What am I missing?

Link *.py files to wing-personal.exe

In Windows 7, I'd like to have the IDE start up as soon as I double click on a *.py file.

While this worked well in previous versions, this is no longer the case for 6.0.7.-1 personal.

What happens now is that the *.py file gets directly executed when I use wing-personal.exe as the standard app for execution.

Using console_wing-personal.exe instead works, but shows an additional nasty console window I'd rather try to avoid.

What am I missing?