> a) This would break a public interface and would need to happen with > deprecation, warnings, etc. That's right we can leave the .init() is of no harm I wouldn't be so afraid anyway Pycuda is still 0.94, so before 1.0 I think there is some degree of freedom in readjusting the interface
> b) Imports with side effects are bad. (pycuda.autoinit is the only > module with side-effects in PyCUDA--and the side effect is its only > purpose.) I agree side effects are bad!! I don't think this is a side effect. This is how you would use the cuda driver. any and I say any function you want from the cuda drivers needs as prerequisite the cuInit(). we save to the user one (important) step, less hassle (did I import autoinit ?) and functions that try to initialize over and over the driver (doesn't harm but .. hey I pay those cpu cycles :P) What the other users say ? Fabrizio -------------------------- Luck favors the prepared mind. (Pasteur) _______________________________________________ PyCUDA mailing list pyc...@host304.hostmonster.com http://host304.hostmonster.com/mailman/listinfo/pycuda_tiker.net