bruno at modulix wrote: > Anton Vredegoor wrote: >> bruno at modulix wrote: >> >>> I still don't get the point. >> >> Well, I've got to be careful here, lest I'd be associated with the >> terr.., eh, the childp..., eh the macro-enablers. >> >> The idea is to have a way to transform a Python (.py) module into XML >> and then do source code manipulations in XML-space using ElementTree. > > My my my... I'm not against the idea of dynamic source code > transformation, but for heaven's sake, *why* would one put XML in the > mix ???????
If a good transform could "reveal" xml as "python's s-expression syntax", not only would source2source transform using xml t2t transform tools be facilitated, but generally speaking it would be easier for "xml retro-coded" python source to find its way through xml-enabled tools&chains. And incite developpers of such tools to consider python a better candidate (eg than it currently is) whenever the matter of scripting the tool comes up. -- http://mail.python.org/mailman/listinfo/python-list
