[issue29399] python3.dll export forwarders not resolved in all situations due to missing python3?.dll dependency and DLL search path behavior

[Steve Dower]

Steve Dower <steve.dower at python.org> added the comment:

I'm not sure we ever meant for LoadLibrary("python3.dll") to actively load the concrete python3X.dll. The APIs are the same, so you can (should) LoadLibrary the one that you want.

It's when you use static imports in extensions that it matters, but in that case it's ensured that both python3X.dll and python3.dll are already loaded.

I guess somewhere we just need to specify that python3.dll is for python3.lib, and not for LoadLibrary? I'm not even sure where the existing documentation is that we would change.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29399>
_______________________________________