Steve Dower added the comment:
I can't vouch for Python 2.2, but Python 3.5 and later should not have any
interference with other Python versions unless you choose to add it to PATH. We
have kept all installed files and registry keys in their own versioned paths
for a long time now.
-
jack added the comment:
If you zap all existing traces of Python and tcl it would affect users
who need to run multiple versions. I would suggest completely
encapsulating each version and all its dependencies, in order to avoid
mutual interference.
On 8/15/2015 2:55 PM, Steve Dower wrote:
> S
Steve Dower added the comment:
Actually, that's a pretty good idea (I'd certainly use it), though it would
come with a big fat warning sign. I'll add an issue for it.
Whether it would fix this particular issue is unclear. I suspect this one is
due to environment variables (TCL_LIBRARY override
Terry J. Reedy added the comment:
> ... why would installing 3.4.3 or other versions be contaminated by stuff
> from another version, especially an ancient one?
I don't know. Steve has revamped the installer for 3.5.
Steve: This issue is solved and I am closing it, but I hope you either have
jack added the comment:
Thanks a lot for the tip. This revealed that Python 3.4.3 was looking
for tcl from Python 2.2 on my machine. That version had been on my
machine more than 10 years ago, but was no longer there. It had left
behind a whole bunch of registry crumbs, which I removed. I then
Terry J. Reedy added the comment:
For 3.4.3, run 'python -m idlelib' in the command window and you should see
some error message. But first run 'python' and at the >>> prompt, 'import
tkinter' to see if tkinter is working properly.
--
nosy: +terry.reedy
__
New submission from jack:
I just installed Python 3.4.3 on a 32-bit machine, 2 GB memory, Win XP SP3.
When I try to start IDLE, pythonw.exe appears briefly in the Windows Task
Manager, then disappears, and nothing else happens. If I run just python.exe in
a command window, that runs OK. The sa
