Alan Kennedy wrote: > [Alan] > >>> Challenge accepted: See my latest post, which explains how jython can >>> do something on Google AppEngine that cpython cannot do: XSLT >>> transforms. >>> >>> Transforming with XSLT on Google AppEngine and jython. >>> http://jython.xhaus.com/transforming-with-xslt-on-google-appengine-and-jython/ >>> >>> I'm looking forward to seeing a comparable cpython implementation ;-) >>> > > [Gerard] > >> Here you go: >> >> http://pastebin.com/f66c44f10 >> > > Sorry, I should have been more specific: I looking to seeing a > comparable cpython implementation which is usable for any XSLT > transform. > > The translation process you undertook to ElementTree was made possible > by the trivial nature of little demo XSLT transform I wrote, which I > did for brevity to fit into a blog post. > > But that approach is unworkable for any real world stylesheet, such as > the DocBook XSLT transforms, which contains more than 180,000 LOC > > http://wiki.docbook.org/topic/DocBookXslStylesheets > > > I know, it was tongue-in-cheek. I was trying to say - "you haven't justified jython until you've justified XSLT, why not use django templates, who cares how you make HTML". But fair enough point about DocBook - stupid real world! I was going to come back with XML database + object binding, but I checked the only python object binder i know of (PyXb) and it fails on the docbook XSD - and in any case you couldn't have an XML database on AppEngine either, so again fair enough. I first met XSLT early in my career and would go round the world to avoid it - it's probably not that bad, but first impressions and all that.
Regards G.F. -- You received this message because you are subscribed to the Google Groups "Python Ireland" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pythonireland?hl=en.
