Mark Hammond schrieb: >> In http://bugs.python.org/issue4120, the author suggests that it might >> be possible to completely stop using the manifest mechanism, for VS >> 2008. Given the many problems that this SxS stuff has caused, this >> sounds like a very desirable route, although I haven't done any actual >> testing yet. >> >> Can all the Windows experts please comment? Could that work? Does it >> have any downsides? >> >> If it works, I would like to apply it to 3.0, although I probably >> won't be able to apply it to tomorrow's rc. Would it also be possible >> to change that in 2.6.1 (even though python26.dll in 2.6.0 already >> includes a manifest, as do all the pyd files)? > > My take is that the bug is suggesting the manifest be dropped only from .pyd > files. Python's executable and DLL will still have the manifest reference, > so the CRT is still loaded from a manifest (FWIW, the CRT will abort() if > initialized other than via a manifest!). What about COM objects: isn't pythoncom26.dll or _ctypes.pyd the first executable image that is loaded first for them? And how would they load the crt? -- Thanks, Thomas
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4