➜

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 paul.moore
Recipients eryksun, jkloth, paul.moore, steve.dower, tim.golden, zach.ware
Date 2021-01-25.18:50:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1611600630.92.0.28258904442.issue43022@roundup.psfhosted.org>
In-reply-to
Content 
So I need to dynamically load *both* python3.dll and python39.dll, but if I do that I can get the functions from python3.dll? What's the point in doing that? Surely I might as well just load python39.dll and get the functions from there, in that case.

I hoped that by using python3.dll, I'd be able to avoid needing to deal with the version-specific DLL at all, so making my code portable to any version of Python 3. I'm pretty sure that's how it works if I statically link to python3.dll...
History
Date User Action Args
2021-01-25 18:50:30paul.mooresetrecipients: + paul.moore, tim.golden, jkloth, zach.ware, eryksun, steve.dower
2021-01-25 18:50:30paul.mooresetmessageid: <1611600630.92.0.28258904442.issue43022@roundup.psfhosted.org>
2021-01-25 18:50:30paul.moorelinkissue43022 messages
2021-01-25 18:50:29paul.moorecreate