Dear all - thanks for your help on this matter! In the end, I was unable to resolve the conflict, so I've gone for a different approach where Cellmodeller and FEniCS run in separate conda environments. Seems to work fine!
Thanks again, W Dr. William P J Smith _____________________________________________ Postdoctoral researcher, Foster lab, University of Oxford On Fri, Jan 25, 2019 at 4:16 PM Andreas Kloeckner <li...@informa.tiker.net> wrote: > Jerome Kieffer <jerome.kief...@esrf.fr> writes: > > > On Fri, 25 Jan 2019 10:00:45 +0000 > > William Smith <willpjsm...@gmail.com> wrote: > > > >> My colleagues and I use PyOpenCL as part of an cell-based modelling > program > >> (Tim Rudge's CellModeller, here < > http://haselofflab.github.io/CellModeller/> > >> ). > >> > >> We would like to use CellModeller alongside a PDE Solver (FEniCS > >> <https://fenicsproject.org/>), whose NumPy requirements (>=1.13) > conflict > >> with those of PyOpenCL (1.9). Is it possible to make PyOpenCL compatible > >> with later NumPy versions? > >> > >> Here's the conflict in my conda environment: > >> > > > > I guess the conflict is related to the conda packaging (poorly done?). > > Hmm, same here. I can't reproduce any part of this. I run CI jobs > involving PyOpenCL and new(-ish?) versions of numpy (>=1.15) all the > time: > > One installed from source: > https://gitlab.tiker.net/inducer/pytential/-/jobs/71311 > > One installed from conda: > https://gitlab.tiker.net/inducer/pytential/-/jobs/71321 > > No issues whatsoever on my end. Are you updating an old (maybe > Py3.5-only?) conda tree? What happens if you update your Python (inside > the conda env)? > > Andreas > _______________________________________________ > PyOpenCL mailing list -- pyopencl@tiker.net > To unsubscribe send an email to pyopencl-le...@tiker.net >
_______________________________________________ PyOpenCL mailing list -- pyopencl@tiker.net To unsubscribe send an email to pyopencl-le...@tiker.net