On Mon, Dec 16, 2013 at 4:01 AM, Steven D'Aprano <steve+comp.lang.pyt...@pearwood.info> wrote: > As I stated earlier, this is just the Interpreter design pattern, with > the minor complication that the domain specific language happens to be an > existing language, Tcl, with an interpreter that usually runs in a > separate process, instead of some mini-language running inside Python.
Yeah, but there's a difference between passing your GUI incantations on to a library function (written in C but now just part of a binary library) and feeding them to a completely different language interpreter. When I write something with PyGTK, I can't, even in theory, give it arbitrary C code to execute. From what I understand here, that *is* true of Tcl, which means that the Python download contains a Python interpreter and a Tcl interpreter. I'm not saying that's a bad thing to do, but it is calculated to provoke remark. ChrisA -- https://mail.python.org/mailman/listinfo/python-list