Movatterモバイル変換

[Python-Dev] DLL in the system directory on Windows.

• Previous message:[Python-Dev] DLL in the system directory on Windows.
• Next message:[Python-Dev] DLL in the system directory on Windows.
• Messages sorted by:[ date ][ thread ][ subject ][ author ]

On Tue, 4 Apr 2000, Mark Hammond wrote:>...> The problem this will lead to is that Python 1.6.0 and 1.6.1 will> not be able to be installed concurrently.Same thing happened with Python 1.5, so we're no worse off. If we do wantthis behavior, then we need to add another version digit...> Putting entries on the> PATH doesnt solve the underlying problem - you will only be able to> have one Python 1.6 directory on your path, else you end up with the> same coflicts for the DLL.>> I dont see any better answer than System32 :-(  Thoughts?I don't have a better answer, as you and I explained on several occasions.Dunno why Guido decided to skip our recommendations, but hey... ithappens :-).IMO, put the DLL back into System32. If somebody can *demonstrate* (nothypothesize) a mechanism that works, then it can be switched.The underlying issue is this: Python16.dll in the app directory works forPython as an executable. However, it completely disables any possibilityfor *embedding* Python. On Windows, embedding is practically requiredbecause of the COM stuff (sure... a person could avoid COM but...).Cheers,-g-- Greg Stein,http://www.lyra.org/

• Previous message:[Python-Dev] DLL in the system directory on Windows.
• Next message:[Python-Dev] DLL in the system directory on Windows.
• Messages sorted by:[ date ][ thread ][ subject ][ author ]