Steve Dower <steve.do...@python.org> added the comment:
Yeah, but in that scenario, it is just as good to LoadLibrary("python39.dll")
and use it as if it was LoadLibrary("python3.dll") because the interaction
model is identical.
The only reason to load python3.dll explicitly is if you are not keeping it
adjacent to python39.dll, and so you need to pre-load it before the interpreter
tries to import a native module. It doesn't provide any benefit for the host
app other than not having to know what DLL you're loading, and most of us
consider a critical security vulnerability rather than a feature ;)
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue29399>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
