➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients Elli Pirelli, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2021-02-25.18:07:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1614276426.92.0.156422599023.issue29399@roundup.psfhosted.org>
In-reply-to
Content 
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.
History
Date User Action Args
2021-02-25 18:07:06steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, eryksun, Elli Pirelli
2021-02-25 18:07:06steve.dowersetmessageid: <1614276426.92.0.156422599023.issue29399@roundup.psfhosted.org>
2021-02-25 18:07:06steve.dowerlinkissue29399 messages
2021-02-25 18:07:06steve.dowercreate