Tomasz Rybak <tomasz.ry...@post.pl> writes:

> On Mon, 2016-11-21 at 22:46 -0600, Andreas Kloeckner wrote:
> [ cut ]
>> At the same time I have a question for you Andreas. There will be
>> > freeze of Stretch on 2017-01-05. I’d like to upload PyOpenCL and
>> > PyCUDA
>> > in mid-December, and those versions will be versions for Stretch.
>> > Do
>> > you plan new releases, or should I just take snapshots from git? 
>> 
>> I'll do a 2016.2.1 mid-December.
>> 
>
> Quick update.
>
> PyOpenCL from 2016-11-30 (commit
> 19015994653dffe2ee407271e19a46e1d6a62796) is in Debian testing,
> for architectures amd64, arm64, armhf, i386, and amd64 and i386
> for kFreeBSD. There is no release-critical errors against it
> which means that this version of PyOpenCL should be in Debian Stretch.
>
> As for PyCUDA, the version in Debian is from 2016-10-24,
> commit 50457813cfe3eb359a230c4e1e546ccdef9947f8.
> It's only available for amd64. I tried to build package
> for ppc64el, but wasn't able to properly configure cross-compiler.
>
> As Debian is in deep freeze now, I won't upload new versions
> of packages Stretch release. Using this time I'll try to
> make ppc64el PyCUDA - but it's not something I'll focus on entirely.
>
> If you have questions or suggestions regarding packages,
> please let me know.

That sounds great. Thank you for continuing to do an excellent job
maintaining PyOpenCL and PyCUDA in Debian!

Andreas


_______________________________________________
PyCUDA mailing list
PyCUDA@tiker.net
https://lists.tiker.net/listinfo/pycuda

Reply via email to