TL;DR: there is no new versions of PyOpenCL nor PyCUDA packages for Debian nor Ubuntu. Details below.
On Mon, 2019-10-07 at 18:47 -0500, Andreas Kloeckner wrote: > Shivangi Agarwal <shivangiagarwa...@gmail.com> writes: > > > Hi, > > > > I installed pyopencl using apt on ubuntu16.04 but it installs an > > older > > version (which doesn't work when CUDA is installed): > > You should be able to just swap out the libOpenCL for a better one > (ocl-icd or Khronos). > > > python-pyopencl/xenial 2015.1-2build3 amd64 > > Python module to access OpenCL parallel computation API > > > > I was wondering if this pkg will be updated to install a new > > pyopencl. > > Not sure, but Tomasz (the package maintainer) might know. > I maintain PyCUDA and PyOpenCL Debian packages. Debian has few suites: unstable (new packages go there), testing (when there is no error in packages in unstable, packages migrate to testing) and stable. Stable is done on basis of testing. Both unstable and testing are rolling releases - new versions of packages are uploaded there. Stable, on the other hand, contains set of unchanging software. Packages are uploaded there only when errors are discovered; and those are not new versions of packages, but only bug fixes. In other words, when stable contains PyOpenCL 2018.1.1, it'll contain this version for ever. Ubuntu (slightly simplifying) takes packages from Debian (unstable and testing), slightly modifies them, adds their own software and fixes, and reelases distribution. Then you can think of it as of Debian stable - so now new version of software. Debian contains something called backports - where some maintainers upload new versions of packages. But this is not enabled by default, and not all packages are available there. For example I don't upload PyCUDA/PyOpenCL to backports. I do not know whether Ubuntu has concept similar to backports - maybe via PPA? But as I am not involved with Ubuntu, I cannot help with that. You can always compile latest version package from source. You can either take PyOpenCL sources from git, or source package from Debian unstable - and then build proper package. This way you'll make sure that it takes care of all dependencies and is properly integrated with rest of system. Best regards. -- Tomasz Rybak, Debian Developer <serp...@debian.org> GPG: A565 CE64 F866 A258 4DDC F9C7 ECB7 3E37 E887 AA8C
signature.asc
Description: This is a digitally signed message part
_______________________________________________ PyOpenCL mailing list -- pyopencl@tiker.net To unsubscribe send an email to pyopencl-le...@tiker.net
