Base-Art - EaseXML

XMLObject mutates to EaseXML

2004-12-12T18:26:00+01:00

In a previous post, i was discussing about Project name clashing. Since then i decided to find a new name for the Python/XML data binding project i’m maintaining … Which is EaseXML !

EaseXML 0.2.0 is out. I hope it won’t collapse with another project now :)

update: The project homepage is now mirrored

Don’t you have your XMLObject yet ? oh sweet heart :(

2004-10-29T13:35:00+02:00

Via DailyPython URL!

Gre7g Luterman: XMLObject_ [XMLObject is a Python module that simplifies the
handling of XML streams by converting the data into objects.]

That’s kind of fun and reminds me the story about Python ALSA wrappers. People do things in their corner. And the final lambda user get lost in the jungle of XXX softwares doing about the same work.

And in this case, especially using the same name for each project. So we have about three different XMLObject projects:

Zope XMLObject .. for Zope,
Base-Art XMLObject,
Last but not least Gre7g XMLObject ..
Not to mention an XmlObject in Java :)

Are you confused ? Well i probably shouldn’t have named my stuff like the Zoped one, i’m guilty here. Finally one more or one left, no difference.

— Reserve your XMLObject jungle map to your favorite receller :)

XMLObject 0.0.1

2004-05-23T21:15:09+02:00

The first release of XMLObject is out. This is a small project I started after writting this post. I tried to apply on Pypi but it seems to be bugged w/ email sending :( Anyway annoucement on Freshmeat should come shortly :)

XMLObject is hosted on http://xmlobject.base-art.net/

— Enjoy !

Of Python and XML

2004-04-21T23:23:02+02:00

Obviously I’m not the first to believe in the power of Python to ease XML management. Of course there are DOM and SAX which are meant to provide uniform (whatever language we use) XML APIs. After using these for a little while, I’m now convinced OO features should be more used, especially meta-programming.

Let’s get an example. For a school IT project, I needed to provide an OO (partial) abstraction of a DTD. So I started making a class for each XML item type defined in the DTD. The process was always the same:

if item A includes a list of B items, there was a need for get/set methods to access the given list
attributes were dealed as Python class variables (__getattr__, __setattr__)

And so on. Then I realized that, the maintenance process would be painfull it the DTD had to be revised. In fact the OO abstraction becomes fully coupled to the DTD.

After that I discovered Python MetaClasses. Python is not the only language to provide meta-programming. But, I find it easier to use than SmallTalk’s one for example. So now we can imagine things like:

class ItemA(XMLObject):
    BItems = XMList(ItemB)
    index = XMLAttribute(type = StringType)

A = ItemA(someXMLData)
print list(A.BItems)
print A.index
A.index = 'foo'

This concept comes directly from SQLObject (Thanks Ian for this great thing). Adapting these design concepts to the (XML, Python) couple would be quite great.