"Martin v. Löwis" <[EMAIL PROTECTED]> writes: > Can you elaborate? To me, that problem only originates from > the OS lack of support for deleting open files. If you could > delete a shared libary that is still in use (as you can on > Unix), the put the new version of the DLL in the place, (...)
Note that at least on NT-based systems, you can at least rename the existing file out of the way while it is in use in order to install a new version. I do think however, that until more recent changes (not sure whether in 2K versus XP) in how DLL searches work (e.g., permitting local versions), even with that operation, if a named DLL was available loaded into memory, it would be used by a subsequent process attempting to reference it regardless of the state of the filesystem. -- David -- http://mail.python.org/mailman/listinfo/python-list
