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

Groups > comp.lang.python > #26924 > unrolled thread

Idle no longer works

Back to article view | Back to comp.lang.python

Contents

  Idle no longer works Opap-OJ <opiney597@yahoo.com> - 2012-08-11 16:09 -0700
    Re: Idle no longer works Benjamin Kaplan <benjamin.kaplan@case.edu> - 2012-08-11 17:30 -0700
    Re: Idle no longer works Terry Reedy <tjreedy@udel.edu> - 2012-08-11 21:59 -0400
    Re: Idle no longer works jussij@zeusedit.com - 2012-08-13 00:11 -0700
      Re: Idle no longer works Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2012-08-13 13:43 -0400
      Re: Idle no longer works Terry Reedy <tjreedy@udel.edu> - 2012-08-13 14:14 -0400

#26924 — Idle no longer works

I can no longer open the Idle IDE for Python on Windows 7.

For 3-5 years I used Idle for all my python work.  But in January this happens:

When I right click on a python file and choose "open with Idle" nothing happens.

If I double-click on the file itself, it briefly opens an MS-DOS looking window, then closes it immediately.

I tried installing Eclipse with PyDev.  It opens the file, but will not run it in Python.

Any idea why?

[toc] | [next] | [standalone]

#26931

On Sat, Aug 11, 2012 at 4:09 PM, Opap-OJ <opiney597@yahoo.com> wrote:
> I can no longer open the Idle IDE for Python on Windows 7.
>
> For 3-5 years I used Idle for all my python work.  But in January this happens:
>
> When I right click on a python file and choose "open with Idle" nothing happens.
>
> If I double-click on the file itself, it briefly opens an MS-DOS looking window, then closes it immediately.
>
> I tried installing Eclipse with PyDev.  It opens the file, but will not run it in Python.
>
> Any idea why?
> --

Have you tried launching Python from the Command Prompt? Open up
command prompt and run C:\Python32\python.exe or whatever corresponds
to your version of Python.

[toc] | [prev] | [next] | [standalone]

#26935

On 8/11/2012 7:09 PM, Opap-OJ wrote:
> I can no longer open the Idle IDE for Python on Windows 7.
>
> For 3-5 years I used Idle for all my python work.  But in January
> this happens:
>
> When I right click on a python file and choose "open with Idle"
> nothing happens.
>
> If I double-click on the file itself, it briefly opens an MS-DOS
> looking window, then closes it immediately.

That should run the file and discard the output. Above is typical

> Any idea why?

*Something* very specific to your system changed. Either registry 
associations for .py are screwed, or your Python installation is 
damaged. Easiest fix is to uninstall and re-install Python. But download 
a more recent version first. Uninstall might not be needed, but makes 
process more like to work.

In the regular interactive command prompt interpreter

import idlelib.idle

should start idle.


-- 
Terry Jan Reedy

[toc] | [prev] | [next] | [standalone]

#26967

On Saturday, August 11, 2012 4:09:16 PM UTC-7, Opap-OJ wrote:

> I can no longer open the Idle IDE for Python on Windows 7.
> ..
> Any idea why?

It looks like your registry has changed.

To fix this just use the Windows Explorer, click on a Python file 
and use the 'Open with, Choose default program' menu and then 
select the Idle IDE as the default program.

[toc] | [prev] | [next] | [standalone]

#27002

On Mon, 13 Aug 2012 00:11:06 -0700 (PDT), jussij@zeusedit.com declaimed
the following in gmane.comp.python.general:

> On Saturday, August 11, 2012 4:09:16 PM UTC-7, Opap-OJ wrote:
> 
> > I can no longer open the Idle IDE for Python on Windows 7.
> > ..
> > Any idea why?
> 
> It looks like your registry has changed.
> 
> To fix this just use the Windows Explorer, click on a Python file 
> and use the 'Open with, Choose default program' menu and then 
> select the Idle IDE as the default program.

	That is probably the worst choice to make -- since what you've
defined means double clicking on ANY .py file will NOT RUN IT -- but
rather attempt to open it with the editor (IDLE)... But since IDLE
itself is a .py file, it may fail to start at all.

	If double-clicking an IDLE.py file does not start it, then the
registry has lost the association of .py to python.exe, not to IDLE. OR
-- .py IS associated to python.exe but the association (the "run
command" is not passing the .py file name to the python executable).

	On WinXP (with ActiveState 2.5.x version) my associations are as:

E:\UserData\Wulfraed\My Documents>assoc .py
.py=py_auto_file

E:\UserData\Wulfraed\My Documents>ftype py_auto_file
py_auto_file="E:\Python25\python.exe" "%1" %*

E:\UserData\Wulfraed\My Documents>

(with similar entries for .pyw to hook into pythonw.exe)
{Just booted the Win7 laptop with Python 2.7.x: The only real difference
is that it uses Python.File where the above has py_auto_file}



-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
        wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

[toc] | [prev] | [next] | [standalone]

#27003

On 8/13/2012 1:43 PM, Dennis Lee Bieber wrote:
> On Mon, 13 Aug 2012 00:11:06 -0700 (PDT), jussij@zeusedit.com declaimed
> the following in gmane.comp.python.general:
>
>> On Saturday, August 11, 2012 4:09:16 PM UTC-7, Opap-OJ wrote:
>>
>>> I can no longer open the Idle IDE for Python on Windows 7.
>>> ..
>>> Any idea why?
>>
>> It looks like your registry has changed.

Most likely, or the Python installation has be damaged.

>> To fix this just use the Windows Explorer, click on a Python file
>> and use the 'Open with, Choose default program' menu and then
>> select the Idle IDE as the default program.
>
> 	That is probably the worst choice to make -- since what you've
> defined means double clicking on ANY .py file will NOT RUN IT -- but
> rather attempt to open it with the editor (IDLE)... But since IDLE
> itself is a .py file, it may fail to start at all.
>
> 	If double-clicking an IDLE.py file does not start it, then the
> registry has lost the association of .py to python.exe, not to IDLE. OR
> -- .py IS associated to python.exe but the association (the "run
> command" is not passing the .py file name to the python executable).
>
> 	On WinXP (with ActiveState 2.5.x version) my associations are as:
>
> E:\UserData\Wulfraed\My Documents>assoc .py
> .py=py_auto_file
>
> E:\UserData\Wulfraed\My Documents>ftype py_auto_file
> py_auto_file="E:\Python25\python.exe" "%1" %*
>
> E:\UserData\Wulfraed\My Documents>
>
> (with similar entries for .pyw to hook into pythonw.exe)
> {Just booted the Win7 laptop with Python 2.7.x: The only real difference
> is that it uses Python.File where the above has py_auto_file}

Re-installing, as I suggested in the first response, is much easier, 
especially for someone not familiar with the above.

-- 
Terry Jan Reedy

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web