Markus Gritsch wrote: > On 25/12/2007, Tim Roberts <[EMAIL PROTECTED]> wrote: > >> Ross Ridge <[EMAIL PROTECTED]> wrote: >> >> >>> Chris Mellon <[EMAIL PROTECTED]> wrote: >>> >>>> What the python installer is doing is the Right Thing for making the >>>> standard python dll available to third party applications. >>>> Applications that want a specific version of a specific DLL should use >>>> the mechanisms available for doing so, instead of relying on there >>>> being a specific version of the python dll in the windows folder. This >>>> is just general best practice on Windows. >>>> >>> No, it's not best practice for an application install any of its files >>> in the Windows system directory. >>> >> Python is more than an application. It's a development tool, and its DLLs >> are needed by any of the Python applications I create. I disagree with >> your assertion. >> > > I assume that your Python applications are .py files. To be able to > run them it would be perfectly ok if the Python DLL would be located > beside the python.exe in the Python installation folder. > > >> Deployment of Python applications is much easier when python24.dll is >> located there. That has to weigh in the equation. >> > > Same doubts as above: For .py files to be executed it is not necessary > that the Python DLL is located in the Windows system32 folder. > > Markus > Another reason "not to put the DLL in win/wys32": on a lot of computers writing to win/sys32 or even the whole C-drive is prohibited !
cheers, Stef -- http://mail.python.org/mailman/listinfo/python-list
