Re: PyXML not supported, what to use next?

2006-10-06 Thread uche . ogbuji
Paul Watson wrote:
 It would appear that xml.dom.minidom or xml.sax.* might be the best
 thing to use since PyXML is going without support.  Best of all it is
 included in the base Python distribution, so no addition hunting required.

FWIW, easy_install [1] is making things so that more and more
installing stuff is not much additional burden.  I'll admit that I've
hardly found easy_install to be problem-free, but since it seems to be
the wave of the future (and a welcome wave at that) I've pushed for
support in recent versions of the XML tools I co-develop: 4Suite [2]
and Amara [3].  For many people these are now very easy to install.
This is the case for some other third-party XML tools as well.

[1] http://peak.telecommunity.com/DevCenter/EasyInstall
[2] http://4suite.org/
[3] http://uche.ogbuji.net/tech/4suite/amara/

--
Uche Ogbuji   Fourthought, Inc.
http://uche.ogbuji.nethttp://fourthought.com
http://copia.ogbuji.net   http://4Suite.org
Articles: http://uche.ogbuji.net/tech/publications/

-- 
http://mail.python.org/mailman/listinfo/python-list


Re: PyXML not supported, what to use next?

2006-10-02 Thread Oliver Andrich
Hi PaulOn 9/30/06, Paul Watson [EMAIL PROTECTED] wrote:
It would appear that xml.dom.minidom or xml.sax.* might be the bestthing to use since PyXML is going without support.Best of all it isincluded in the base Python distribution, so no addition hunting required.
Is this right thinking?Is there a better solution?I am using lxml as my standard tool of choice. It includes the easy interface of ElementTree and the speed and power of being backed by libxml2 and libxslt. But this mainly cause I have to deal with large XMLs in a fast way. Otherwise pure ElementTree is a very, very nice choice. And it is also our backup choice, when lxml is not available on a system.
Best regards,Oliver-- Oliver Andrich [EMAIL PROTECTED] --- http://roughbook.de/
-- 
http://mail.python.org/mailman/listinfo/python-list

PyXML not supported, what to use next?

2006-09-30 Thread Paul Watson
It would appear that xml.dom.minidom or xml.sax.* might be the best 
thing to use since PyXML is going without support.  Best of all it is 
included in the base Python distribution, so no addition hunting required.

Is this right thinking?  Is there a better solution?
-- 
http://mail.python.org/mailman/listinfo/python-list


Re: PyXML not supported, what to use next?

2006-09-30 Thread John Salerno
Paul Watson wrote:
 It would appear that xml.dom.minidom or xml.sax.* might be the best 
 thing to use since PyXML is going without support.  Best of all it is 
 included in the base Python distribution, so no addition hunting required.
 
 Is this right thinking?  Is there a better solution?

You can try ElementTree, it comes with 2.5 (xml.etree.ElementTree).
-- 
http://mail.python.org/mailman/listinfo/python-list


Re: PyXML not supported, what to use next?

2006-09-30 Thread Paul Boddie
John Salerno wrote:
 Paul Watson wrote:
  It would appear that xml.dom.minidom or xml.sax.* might be the best
  thing to use since PyXML is going without support.  Best of all it is
  included in the base Python distribution, so no addition hunting required.
 
  Is this right thinking?  Is there a better solution?

 You can try ElementTree, it comes with 2.5 (xml.etree.ElementTree).

Certainly, ElementTree, xml.sax and xml.dom.minidom appear to be viable
as standard library solutions for the foreseeable future. Sadly, Python
XML activities have fragmented since PyXML was in its prime,
reminiscent of that other contentious area of Python standardisation:
Web technologies.

Paul

-- 
http://mail.python.org/mailman/listinfo/python-list