On Aug 12, 2015 16:49, "Robert Collins" <robe...@robertcollins.net> wrote:
>> I'm not sure what will be needed to get the PR accepted; At PyCon AU> Tennessee Leuwenberg started drafting a PEP for the expression of> dependencies on e.g. BLAS - its been given number 497, and is in the> packaging-peps repo; I'm working on updating it now.
I wanted to take a look at this PEP, but I can't seem to find it. PEP 497:
appears to be something else entirely?
I'm a bit surprised to hear that such a PEP is needed. We (= numpy devs)
have actively been making plans to ship a BLAS wheel on windows, and AFAICT
this is totally doable now -- the blocker is windows toolchain issues, not
Specifically the idea is to have a wheel that contains the shared library
as a regular old data file, plus a stub python package that knows how to
find this data file and how to make it accessible to the linker. So
numpy/__init__.py would start by calling:
# on Linux modifies LD_LIBRARY_PATH,
# on Windows uses ctypes to preload... whatever
and then get on with things, or the build system might do:
This doesn't help if you want to declare dependencies on external, system
managed libraries and have those be automatically somehow provided or
checked for, but to me that sounds like an impossible boil-the-ocean
project anyway, while the above is trivial and should just work.
Distutils-SIG maillist - Dist...@python.org