Dnia 2012-10-28, nie o godzinie 14:16 +0200, Tomi Pieviläinen pisze:
passes strings to OpenCL functions. PyCUDA needs to
call nvcc and it uses pytools.preforrk.call_capture_output to do so.
call_capture_output uses Popen.communicate() - which returns buffer,
not string. Then PyCUDA tries to find some string in the output -
and we have type mismatch between string and buffer. I am not sure
whether pytools or PyCUDA needs fixing. Any thoughts, Andreas?
If needed, I think I could take a quick stab in poting pycuda to py3k.
With 3.3 it's even simpler than before to create crosscompatible
version. That is, if 3.0-3.2 don't need to be supported.
I'd say go for 3.3 for now. From my point of view it would be
better to have PyCUDA working on Python 3.2 (the Debian version)
but having it working on any Python 3 will be better. Later
we can think of extending Python 3 support to earlier versions.
I've been thinking about situation and whether to change pytools
or PyCUDA. Pytools is just a wrapper around Popen and it could be
strange for it to return objects with types different from those
returned by Popen. So it seems more natural to deal with it in PyCUDA.
Just my 2cents.
Tomasz Rybak GPG/PGP key ID: 2AD5 9860
Fingerprint A481 824E 7DD3 9C0E C40A 488E C654 FB33 2AD5 9860