> No, that doesn't follow from the requirements given. The only exception > for something that isn't a service or device driver is for backwards > compatibility. Also, pretty much any DLL supports side-by-side > installation.
Hmm. How do I have to build and install python25.dll exactly to make that work? How do applications have to link against it? > The backwards compatibility exception doesn't apply when the name of > the DLL changes. Chapter and verse of the spec? > If the name of the DLL changes, the shared location > its installed to can also change. No. The existing applications still require Python to be located on the path, even if they are rebuilt against the new DLL. This is source backwards compatibility, not binary backwards compatibility. Regards, Martin -- http://mail.python.org/mailman/listinfo/python-list
