You're right guys, option 2 is a much better compromise for everyone.
> I would prefer option 2.
> Installing an additional package such as Mako is not a big deal if you
> administrate a single-user system. But if you have a cluster with many users
> and a large number of request for new software or don't have administrative
> privileges and want to install things as user additional dependencies make
> life harder.
+1 on this. Don't force a templating engine on people for non-required
aspects of PyOpenCL. Use cases: someone using the package to run
"vanilla" OpenCL code from Python, or writes their
meta-programming OpenCL code with a different templating engine
shouldn't have the "burden" of installing another templating
314 address only used for lists, off-list direct email at:
| GPG/PGP key id: 0x0F3E28F7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
-----END PGP SIGNATURE-----
PyOpenCL mailing list