On 3/29/2014 7:28 PM, Michael Hipp
wrote:
On 3/29/2014 4:27 PM, Bob Klahn
wrote:
Under *HKEY_CLASSES_ROOT*, these
subtrees remain: py_auto_file, pysFile,
Python, Python.AXScript2, Python.Dictionary,
PythonDictionary.1,
Python.File, Python.Interpreter, Python.Interpreter.2,
Python.NoConFile,
Python.Test.Pippo, Python.Test.PyCOMTest, and
Python.Test.PyCOMTestMI.
Under *HKEY_LOCAL_MACHINE | Software*, subtree Python
remains, with
PythonCore subtrees 2.4, 2.5, 2.6, and 2.7.
I'm thinking I should go into *regedit* and delete all
of those
subtrees. Super-carefully of course. I have to say,
I’m surprised that
all these registry entries are still there!
Yes, what I'm talking about now are Python issues rather
than wxPython
issues, but they've arisen because of my wxPython
problems, so I think
this discussion is still appropriate here.
Steve, Michael, do you agree that I should delete the
left-over Python
registry entries I listed above? I'm all ears.
Quivering ears.
I never delved into any python-related registry entries,
so I can’t
speak with any authority on it. But in all the times I've
uninstalled
and re-installed python (et al) I've never had to do so.
My advice: after uninstall, delete the c:\pythonXX folders
and
c:\program files\wxpython-related folders, reinstall
py+wxpy and try
it. It should work. And if it doesn't, the whole exercise
doesn’t take
very long. I've done it many times. Once everything is
downloaded, the
installs go quickly.
If you wanted to attempt a really clean uninstall,
consider
downloading Revo Uninstaller Portable and use it (I use it
extensively
in malware cleanups). It could likely clean up those
leftover registry
entries much safer than you could do it yourself.
Michael
I went ahead and carefully deleted the Python-related
Windows registry
trees, then re-installed Python 2.7, build 214 of Mark
Hammond’s Windows
extensions, wxPython 3.0.0.0, and the wxPython 3 demo. I
documented the
registry changes after each of these installs.
/*TO NO AVAIL. The wxPython demo still fails, the same
way: I get the
splash screen, then a second or two later this error message
pops up:
"pythonw.exe has encountered a problem and needs to close.
We are sorry
for the inconvenience. ..." *//*
*/
And my application is still exhibiting the same issues.
Fatal issues.
For the work I do, this is super-serious. Without the
wxPython demo,
all I know to do is to continue to plod along, trying to fix
code that
worked just fine, for years, under Python 2.5.4 and wxPython
2.8.10.1.
Python 2.7.6 works and Mark Hammond's Windows extensions
work. Parts of
my wxPython application work, but the most important parts
do not.
/*Does anyone here have any idea why the wxPython demo won't
run?*/ As
I've previously reported, I used
wxPython3.0-win32-docs-demos-3.0.0.0.exe to install it.
Again, I'm running Windows XP Service Pack 3. (I have to,
because of
other software that cannot run on more recent Windows
versions.)
specified the path of the python executable. Does it print
anything to the console before it dies?