PyXML XPath and XSLT Re: [XML-SIG] Mass assignment of 4Suitebug reports

Uche Ogbuji uche.ogbuji@fourthought.com
Tue, 10 Sep 2002 13:36:50 -0600


> > I'm all for this.  What I would like to see then in xml.xpath and
> > xml.xslt is smart import logic similar that in the default xml.
> > 
> > So, if a user tries to import xml.xslt.processor it will first look to
> > see if Ft.Xml.Xslt.Processor is available, and if not, then try
> > xml.pyxslt.Processor.  Or, any other of the xslt processors that
> people
> > are proposing.
> 
> Please don't do this. The smart import used by PyXML has caused me
> serious problems in the past.

You mean _xmlplus?  I think this is a very different matter.


> Unless the two libraries are going to be bug for bug compatible, then
> I'd like to be able choose myself.

But you can always do this, right?  You can just directly import what you 
want.  This is different from _xmlplus which *masks* the overriden modules.  
Under Mike's proposal, all the various modules would still be available for 
explicit import.


-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
Track chair, XML/Web Services One Boston: http://www.xmlconference.com/
Basic XML and RDF techniques for knowledge management, Part 7 - http://www-106.ibm.com/developerworks/xml/library/x-think12.html
Keeping pace with James Clark - http://www-106.ibm.com/developerworks/xml/library/x-jclark.html
Python and XML development using 4Suite, Part 3: 4RDF - http://www-105.ibm.com/developerworks/education.nsf/xml-onlinecourse-bytitle/8A1EA5A2CF4621C386256BBB006F4CEC