I've started to fix this hole in the SCA C++ Python support.
Looking at the various options, ElementTree seems the simplest, most "Pythonic" XML library to use - this is included in Python 2.5, but I don't think it is in earlier versions so we'll need to up our required Python level to 2.5 or provide the details of how to add ElementTree support (which is very simple - the library is written in Python and claims to be runnable on 1.5.2 and later). In the future it may be good to have something more SDO-ish - what do people think? Cheers Andy On 10/2/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
[snip] > On 9/22/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: >> To allow Python components to handle more than just simple data types, >> we need to decide how we present structured data / complex types to >> Python components. We'll probably want to support many more data binding >> options in the future, but we need one simple solution as a starting >> point. >> >> For Ruby I have implemented support for Rexml for now mainly because >> it's included in the Ruby distribution. What do you guys think we should >> use for Python? >> - an xml.dom or xml.minidom - from the Python standard library >> - an xml.ElementTree - more pythonic and nicer rendering, recent >> addition to the Python 2.5 standard library (just released on Sept >> 19th), available as a separate package on older releases >> - a new implementation of a Python transcription of the SDO API? >> >> Here's what I was thinking about: >> - step 1, soon - ElementTree >> - step 2, longer term - an SDO API >> >> Any thoughts? >> >> -- >> Jean-Sebastien >> Andrew Borley wrote: [snip] > Yep, I was thinking about this too - I think you're right that we need > something soon (and basing it on an XML technology that's already > available is the right way to do this) and then an SDO API later > (probably wrappering the C++ implementation, in a similar way to the > PHP SDO package). > > We're going to need something if we want to include the support for Python in our M2 release. I was rereading this thread and I'm not sure that we've clearly identified how we're going to present structured data to Python scripts (coming from a Web Service for example). Any more thoughts? Do people prefer: - ElementTree? - A flavor of DOM? - the SDO API wrapped in SWIG? - a more Pythonic rendering of the SDO API? Any Python developers out there would like to jump in and tell us their preference? -- Jean-Sebastien --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
