IDLE won't run after installing Python 3.3 in Windows

[eglowstein.h]

The next adventure in Python was to install Python 3 into a Windows XP machine. I had a previous 2.7 installation that I uninstalled and carefully removed all traces of from the directory and the registry.

I got the 'python-3.3.3.msi' from Python.org and installed it. From a command window I can run 'python' and I get the Python prompt. I have several Python programs on the machine. If I right click o one, I have the option of 'Edit in IDLE'. If I do that, the disk light blinks briefly, and then nothing. So I went into the \python33\lib\idlelib directory and from a CMD window, ran 'python idle.py'. That loads IDLE. but when I ask IDLE to load a file, it navigates to a FileOpen dialog and then closes everything when I actually open the file. I then tried the same thing but used 'pythonw' instead.Same deal.

I also saw some other threads here about how Python can get befuddled by firewalls, so I disabled that with no effect.

Any suggestions? Thanks in advance!

Howard

 

[behrooz.abbasy]

The next adventure in Python was to install Python 3 into a Windows XP machine. I had a previous 2.7 installation that I uninstalled and carefully removed all traces of from the directory and the registry.



I got the 'python-3.3.3.msi' from Python.org and installed it. From a command window I can run 'python' and I get the Python prompt. I have several Python programs on the machine. If I right click o one, I have the option of 'Edit in IDLE'. If I do that, the disk light blinks briefly, and then nothing. So I went into the \python33\lib\idlelib directory and from a CMD window, ran 'python idle.py'. That loads IDLE. but when I ask IDLE to load a file, it navigates to a FileOpen dialog and then closes everything when I actually open the file. I then tried the same thing but used 'pythonw' instead. Same deal.



I also saw some other threads here about how Python can get befuddled by firewalls, so I disabled that with no effect.



Any suggestions? Thanks in advance!



Howard

 

[Mark H. Harris]

Any suggestions? Thanks in advance!

Switch to Gnu/Linux. <sorry, couldn't resist>

Which version of tcl/tk is installed. I would guess that tkinter is honked up somehow... did you clear up the old tkinter stuff?

 

[Mark Lawrence]

Switch to Gnu/Linux. <sorry, couldn't resist>

Which version of tcl/tk is installed. I would guess that tkinter is honked up somehow... did you clear up the old tkinter stuff?

The version of tcl/tk is completely irrelevant as it comes bundled in
the Python msi installer.

 

[Mark H. Harris]

The version of tcl/tk is completely irrelevant as it comes bundled in

the Python msi installer.

Does the previous version put stuff into the registry that keeps the new version from running correctly?

 

[Mark Lawrence]

Does the previous version put stuff into the registry that keeps the new version from running correctly?

Not that I'm aware of. But then again if people knew the answer it
would have been posted by now. Where is Terry Reedy when you need him?
Or possibly rr for that matter?

 

[Terry Reedy]

On 19/02/2014 17:30, Mark H. Harris wrote:

Not that I'm aware of. But then again if people knew the answer it
would have been posted by now. Where is Terry Reedy when you need him?

Puzzled as to what the problem is.

 

[eglowstein.h]

Puzzled as to what the problem is.

I was extremely careful to remove any last bit of evidence in the registry that *anything* in the c:\python27 and c:\python33 directories ever existed.. After the registry was purged of everything and I deleted the directories, I restarted the machine to make sure the registry was read afresh (Windows XP is wacky that way) and then did a reinstall of Python 3.3.3. Before installing anything else, I launched a program by using the 'Edit in Idle' option. Idle comes up, flashes briefly and exits. The console window never appears. If I bring up a command window and go into the lib\idlelib directoryand specifically start idle with "python idle.py" or "pythons idle.py", I get Idle, but no command window. Load a file in if launched with 'python', it appears but you can't run it. If you launch with 'pythons', the whole kit & caboodle just exits when you load the file.

That might not help, but that's all I saw. Is there someplace not obvious in the registry where any interesting information is kept?

 

[David Robinow]

The next adventure in Python was to install Python 3 into a Windows XP machine. I had a previous 2.7 installation that I uninstalled and carefully removed all traces of from the directory and the registry.

It is not necessary to uninstall previous versions of Python. They
can live happily together. Not only does it work, it's a supported
configuration. That's what the launcher is for.
Mucking with the registry is generally inadvisable. It's too easy to
make a mistake.
If you do decide to uninstall a Python version, do it through the
Control Panel. If that results in problems, submit a bug report.

I got the 'python-3.3.3.msi' from Python.org and installed it. From a command window I can run 'python' and I get the Python prompt. I have several Python programs on the machine. If I right click o one, I have the option of 'Edit in IDLE'. If I do that, the disk light blinks briefly, and then nothing. So I went into the \python33\lib\idlelib directory and from a CMD window, ran 'python idle.py'. That loads IDLE. but when I ask IDLE to load a file, it navigates to a FileOpen dialog and then closes everything when I actually open the file. I then tried the same thing but used 'pythonw' instead. Same deal.

I also saw some other threads here about how Python can get befuddled by firewalls, so I disabled that with no effect.

Any suggestions? Thanks in advance!

I would reinstall Python2.7 and then reinstall Python3.3. That may
straighten out your registry. (It may not)
Let us know if that works.

 

[flebber]

Well firstly being windows I assume that you did a restart after install.

Python.org python doesn't come with the windows extensions which can be installed separately.

On windows I use winpython is totally portable and can be installed as system version includes all extensions as well as Numpy and matplotlib etc which can be a bit tricky to install otherwise.

There is enthought and anaconda packaged python a well but my choice is winpython

Give it a try and you'll definitely have a working system version.

Sayth

 

[Mark H. Harris]

Any suggestions? Thanks in advance!

Is there any possibility that you are bumping up against open IDLE Issue 14576?

http://bugs.python.org/issue14576