My 2c: numpy has already dropped Python 2 in release 1.17. I see little to no benefit to keep producing new PyOpenCL releases that integrate against obsolete numpy releases... if one (I feel sorry for him) still needs Python 2, he should just stick to old numpy AND old PyOpenCL.
Cheers Guido On Tue, 3 Sep 2019 at 15:55, Andreas Kloeckner <li...@informa.tiker.net> wrote: > Santiago Torres-Arias <santi...@archlinux.org> writes: > > > On Mon, Sep 02, 2019 at 09:57:52PM +0200, Tomasz Rybak wrote: > >> Hello. > >> > >> I sent similar email to more mailing lists, all related to PyGPGPU > >> packages. Sorry if you receive this many times; I'll follow all replys. > > > > Hi! > > > > I know this is somewhat unrelated, but we've dropped py2 as of > > 2019.1 as part of our py2 deprecation efforts on Arch Linux. We've yet > > to receive any complaints about it :) > > Off-off-topic, but thanks again to the both of you for your effort > maintaining packages of PyOpenCL! > > From my perspective, I have no objections to dropping Py2 rather sooner > than later, though I plan to keep supporting Py2 in both packages until > Py2 EOL,i.e. the beginning of the new year. > > 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
