On Dienstag 02 März 2010, Bogdan Opanchuk wrote:
like pycudafft to be part of PyCUDA itself, we can
discuss how that could happen.
I am not sure it is necessary. There is *nix ideology, which favors
separated functionality. And you will have to add mako templating
engine as a dependency for pycuda. But the final decision about
architecture of your package is on you of course; it is not a problem
for me to compose corresponding patch. I already changed plan
interface a little in order to make it use shape/dtype parameters in a
same way as numpy arrays and pycuda.gpuarrays.
It's a double-edged sword, IMO. The simple-small-modular approach has
obvious maintainability advantages. On the other hand, an integrated
package is more convenient to install and depend on. I'll leave this up
to you to decide.
For now, I've added a link to pycudafft to the docs: