Steve Dower <[email protected]> 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 <[email protected]>
<https://bugs.python.org/issue29399>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
