Or you could just create a Python package that only contains the dll, and depend on it from your others.
On Tue, Sep 30, 2014 at 10:44 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > On 1 October 2014 00:37, Paul Moore <p.f.mo...@gmail.com> wrote: >> On 30 September 2014 15:31, David Genest <david.gen...@ubisoft.com> wrote: >>> Ok, so what if the dll is shared in a given environment (multiple >>> extensions use it)?, the shared dll should be copied to every package? >>> Won't that cause multiple loads by the system? >> >> I honestly don't know in that case, sorry. You might get a better >> answer on python-list for that, if no-one here can help. >> >> Presumably the usage is all within one distribution, otherwise the >> question would have to be, which distribution ships the DLL? But that >> question ends up leading onto the sort of discussion that starts >> "well, I wouldn't design your system the way you have", which isn't >> likely to be of much help to you :-( >> >> Sorry I can't offer any more help. > > Note that this is the external binary dependency problem that the > scientific folks are currently using conda to address. It's basically > the point where you cross the line from "language specific packaging > system" to "multi-language cross-platform platform". > > That said, pip/wheel *may* get some capabilities along these lines in > the future, it just isn't a high priority at this point. > > Cheers, > Nick. > > -- > Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
