Hi Andreas, Great I will do that today. I also made a Conda recipe for pyopencl, along with a few dependencies (appdirs, mako and pytools), which I was going to upload to binstar. Then “conda install pyopencl” should work. Any objection to this?
Tim > On 5 Feb 2015, at 20:41, Andreas Kloeckner <[email protected]> wrote: > > Hi Tim, > > Tim Rudge <[email protected]> writes: >> I am trying to get pyopencl installing with pip (as a dependency in my own >> distribution). However I get "ImportError: No module named numpy” during >> setup. >> >> This seems to be an issue with organisation of numpy installation - see here >> http://stackoverflow.com/questions/19919905/how-to-bootstrap-numpy-installation-in-setup-py. >> >> >> Installation works perfectly if I do “pip install numpy” before “pip install >> pyopencl”. >> >> So, apparently there is a workaround for setuptools using: >> >> __builtins__.__NUMPY_SETUP__ = False >> >> I also noticed that in the current setup.py there is only >> setup_requires=[“numpy”], whereas it should also be in install_requires. >> >> After modifying setup.py as attached “pip install -e pyopencl” (where I am >> pointing at my local source) seems to work fine and installs numpy and other >> dependencies. >> >> If this is a sensible way to fix this issue, I’ll be happy to >> push/pull_request these changes. > > Thanks for figuring this out. At this point, I can't see a downside to > merging this, so I'd say let's go for it. When you put together the pull > request, please link to this discussion, here: > > http://lists.tiker.net/pipermail/pyopencl/2015-February/001860.html > > Andreas > _______________________________________________ PyOpenCL mailing list [email protected] http://lists.tiker.net/listinfo/pyopencl
