Re: [Python-checkins] CVS: python/dist/src/PCbuild python20.wse,1.6,1.7
Update of /cvsroot/python/python/dist/src/PCbuild In directory slayer.i.sourceforge.net:/tmp/cvs-serv25776
Modified Files: python20.wse Log Message: Thomas Heller noticed that the wrong registry entry was written for the DLL. Replace %_SYSDEST_%\Python20.dll with %_DLLDEST_%\Python20.dll.
Unfortunately, there was a bug in my bug-report. %DLLDEST% would have been correct. Sorry: Currently I don't have time to test the fix. Thomas Heller
Modified Files: python20.wse Log Message: Thomas Heller noticed that the wrong registry entry was written for the DLL. Replace %_SYSDEST_%\Python20.dll with %_DLLDEST_%\Python20.dll.
Unfortunately, there was a bug in my bug-report.
Actually, there is no need to write that entry at all! It should be removed. I thought it was, ages ago. Mark.
Modified Files: python20.wse Log Message: Thomas Heller noticed that the wrong registry entry was written for the DLL. Replace %_SYSDEST_%\Python20.dll with %_DLLDEST_%\Python20.dll.
Unfortunately, there was a bug in my bug-report.
Actually, there is no need to write that entry at all! It should be removed. I thought it was, ages ago. I would like to use this entry to find the python-interpreter belonging to a certain registry entry.
How would you do it if this entry is missing? Guess the name python<major-version/minor-version>.dll??? Thomas Heller
[Me, about removing the .DLL entry from the registry]
Actually, there is no need to write that entry at all! It should be removed. I thought it was, ages ago.
[Thomas]
I would like to use this entry to find the python-interpreter belonging to a certain registry entry.
How would you do it if this entry is missing? Guess the name python<major-version/minor-version>.dll???
I think I am responsible for this registry entry in the first place. Pythonwin/COM etc. went down the path of locating and loading the Python DLL from the registry, but it has since all been long removed. The basic problem is that there is only _one_ acceptable Python DLL for a given version, regardless of what that particular registry says! If the registry points to the "wrong" DLL, things start to go wrong pretty quick, and in not-so-obvious ways! I think it is better to LoadLibrary("Python%d.dll") (or GetModuleHandle() if you know Python is initialized) - this is what the system itself will soon be doing to start Python up anyway! Mark.
From: "Mark Hammond" <MarkH@ActiveState.com> To: "Thomas Heller" <thomas.heller@ion-tof.com>, <python-dev@python.org> Date: Tue, 22 Aug 2000 23:32:25 +1000
Modified Files: python20.wse Log Message: Thomas Heller noticed that the wrong registry entry was written for the DLL. Replace %_SYSDEST_%\Python20.dll with %_DLLDEST_%\Python20.dll.
Unfortunately, there was a bug in my bug-report.
Was that last like Thomas Heller speaking? I didn't see that mail! (Maybe because my machine crashed due to an unexpected power outage a few minutes ago.)
Actually, there is no need to write that entry at all! It should be removed. I thought it was, ages ago.
OK, will do, but for 2.0 only. --Guido van Rossum (home page: http://www.pythonlabs.com/~guido/)
participants (3)
-
Guido van Rossum -
Mark Hammond -
Thomas Heller