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 lemburg
Recipients Ray Donnelly, barry, brett.cannon, eryksun, lemburg, njs, paul.moore, steve.dower, tim.golden, xoviat, zach.ware
Date 2018-01-17.08:35:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <60a04c66-e4df-98d6-1d3f-470c5def4914@egenix.com>
In-reply-to <1516153950.09.0.467229070634.issue32516@psf.upfronthosting.co.za>
Content
On 17.01.2018 02:52, xoviat wrote:
> 
> xoviat <xoviat@gmail.com> added the comment:
> 
> For the record, moving the DLL path manipulation code into the interpreter would address the concern that importing a module would not manipulate the search path because the behavior would move into Python itself.

Can't you simply place the DLLs into the PythonXX\DLLs\ directory ?

That's where Python itself keeps external DLLs (and several PYDs)
and it won't change after installation of Python.

Or create a special container package on PyPI into which you place
the DLLs and add dependencies to this in all other packages.

You can then load the DLL via win32 LoadLibrary either using the
Python win32 tools or ctypes:

https://docs.python.org/3.7/library/ctypes.html
http://timgolden.me.uk/pywin32-docs/win32api__LoadLibrary_meth.html
https://www.programcreek.com/python/example/51388/win32api.LoadLibrary

FWIW: I think this ticket has shown plenty options to possible
solutions, including many which do not manipulate the path.
History
Date User Action Args
2018-01-17 08:35:43lemburgsetrecipients: + lemburg, barry, brett.cannon, paul.moore, tim.golden, njs, zach.ware, eryksun, steve.dower, xoviat, Ray Donnelly
2018-01-17 08:35:43lemburglinkissue32516 messages
2018-01-17 08:35:42lemburgcreate