Dirk Meyer wrote: > Duncan Webb wrote: >> beats me, attached are the two listings. >> >> Duncan >>>>> import kaa.metadata.version >> File "/usr/lib/python2.4/site-packages/kaa/xmlutils.py", line 34, in ? >> import xml.sax >> ImportError: No module named sax >>>>> import xml.sax >>>>> dir(xml.sax) >> ['ContentHandler', 'ErrorHandler', 'InputSource', 'SAXException', >> 'SAXNotRecognizedException', 'SAXNotSupportedException', >> 'SAXParseException', 'SAXReaderNotAvailable', '__builtins__', '__doc__', >> '__file__', '__name__', '__path__', '_exceptions', 'handler', 'make_parser', >> 'parse', 'parseString', 'sax2exts', 'saxexts', 'saxlib', 'xmlreader'] > > Oops, my fault. > > To everyone playing with the current svn of kaa.base and > kaa.metadata. I removed kaa.xml which was a bad wrapper for > libxml2. This file was named xml.py in the base dir and conflicts with > the global python xml import. If you use kaa.base svn, remove the > build dir (use python setup.py clean in the kaa root dir to be sure) > and delete the installation of kaa in site-packages. If you get the > error from above, xml.py[co] is still installed and conflicts with the > global xml installation. > > The same is true for kaa.metadata. In misc was a file called xml.py > which conflicts with the global python install. It is renamed now.
Ah thanks, should have thought of doing a full clean. Duncan ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
