First - general comment.
I quite like an idea of changing PyOpenCL to work with PyPy.
Can I assume that this is just for PyOpenCL, and PyCUDA stays
Boost (and thus CPython) only for now?
I do not know yet how packaging will look like for package
that both supports CPython and PyPy - I'll need to check that.
As for testing in the wild - if I'm able to build PyPy
version I hope to be able to upload it to Debian experimental,
so interested Debian users could test it. I think that
some separate versioning for PyPy version will help here.
Dnia 2014-05-28, śro o godzinie 09:09 -0500, Andreas Kloeckner pisze:
Bogdan Opanchuk <mantihor(a)gmail.com> writes:
On Wed, May 28, 2014 at 4:04 PM, Andreas Kloeckner
- PyOpenCL's array and algorithms
functionality will be spun off into
separate packages ("clarray" and "clalgorithms"?).
Isn't `compyte` supposed to be the array package (and I remember it
containing some algorithms as well)? Will its status change somehow?
Compyte has a role across PyCUDA and PyOpenCL. The things I'm describing
here are CL-only.
As for that - I am not sure how it'll influence packaging.
For now I am fetching compyte during both PyOpenCL and PyCUDA
build, so each of them carries own copy of compyte.
But if there is more shared code, or more separate modules, I might
consider creating additional packages; it such a case detailed
documentation describing what depends on what and what are
interconnections will definitely help.
Tomasz Rybak GPG/PGP key ID: 2AD5 9860
Fingerprint A481 824E 7DD3 9C0E C40A 488E C654 FB33 2AD5 9860